Skip to content
This repository has been archived by the owner on May 9, 2022. It is now read-only.

The future of spid-testenv2 #332

Open
peppelinux opened this issue Mar 25, 2021 · 0 comments
Open

The future of spid-testenv2 #332

peppelinux opened this issue Mar 25, 2021 · 0 comments
Labels
breakage help wanted Extra attention is needed

Comments

@peppelinux
Copy link
Member

peppelinux commented Mar 25, 2021

spid-testenv2 will be rewritten above the django framework and spid-sp-test such as to make it:

  • suitable for production
  • capable of managing different storage engines (via ORM)
  • capable of registering new SPs through authentication (SAML2 SPID optionally activated)

spid-testenv2 doesn't represent an alternative to spid-saml-check because the latter is a highly specialized unit test platform, while spid-testenv2 wants to offer itself as a demonstrative SPID IDP, as similar as possible to those in production in the world real.

However, future releases of spid-testenv2 and spid-saml-check will adopt a single test suite, namely [spid-sp-test] (https://github.com/italia/spid-sp-test) so as to offer all developers a unified test behavior, regardless of the chosen platform.

The current code of the project will be moved to a branch called old, the old issues will be converted to the new project or, if deemed out of context, simply closed, the same for the current active roadmaps. Pull Requests will be closed.

@alranel @bfabio @sebbalex thank you for being here

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
breakage help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant