...
Bookmark this page for the Practitest Test Sets view (where testers will typically start) https://stage.practitest.com/p/5023/sets
Note that while we track testing in PractiTest, we don’t track bugs/issues there - we use GitHub issue tracking. Raise a GitHub issue in the appropriate repo (Safe Paths or Safe Places).
https://github.com/tripleblindmarket/safe-places
Also, GitHub issues are for clear product bugs. If you are raising a concern about the spec, requirements or capabilities of the product, you should raise in Jira instead.
More specific briefing on this to be developed, but the Safe Paths & Safe Places projects can be found here:
https://pathcheck.atlassian.net/secure/BrowseProjects.jspa
Pracitest asks:
Additonal admins welcome - let us know if you want to.
We want people to keep developing our library of Tests on Practitest, and to keep evolving how we use the platform. Joel Montvelisky (VP Product at PractiTest, in Israel), has offered some of his time to help us understand how to make the platform work best for us. We don’t want to flood him with enquiries, but if you think you can make good use of his time, get a contact from Diarmid or Vedha. (for more basic questions, there is also a support channel for the PractiTest Website
More documentation here on how we are using / structuring PractiTest, hints & tips, lessons learned, ideas/vision for the future - bring it all on here! (create some pages below this one).
...