To Software Software - To Software-Assessment - Software/Assessment - To Software/CurrentTest

Testers and Developers Frequently Asked Questions (FAQ)

The new Testserver is under the Software-Assessors authority as the central, final Testsystem before patches are bundled into a new Revision for the production system.
See Software/Assessment/testserver for details, or use the link https://test.cacert.org

Correct. The new testserver has no direct outbound email communications enabled. All mails are redirected by the internal firewall to the Testserver Mgmt System
Once, you have created an account, please switch to the Testserver Mgmt System, login with the account you have created under https://mgr.test.cacert.org:14843/login with the password you have set.
Under Mail Account you can access your mails that relates to your account
Also here you'll find your confirmation mail with the confirmation link

For all account manipulations, please go onto the Testserver Mgmt System website
Login with your account of test.cacert.org under https://mgr.test.cacert.org:14843/login you want to modify $/!\$ Note: We have experienced problems with Testserver Mgmt logins if the password contains non ASCII characters! This is considered a bug, we are working to fix it, and of course you can try them non-ASCII passwords anyway, but it may cost you less time to restrict your password to ASCII.
Enter the Manage Account link
Use one of the Manage Account links
- Automated Assurance - to trigger assurances you receive to your account (like real assurances, 35 pts max each, upto 100 points)
- Administrative Increase - to trigger an administrative increase (i.e. 150 points total)
- Assurer Challenge - trigger your account so that you have passed the Assurer Challenge
- Set Flags - Set additional special flags (i.e. Support-Engineer, OrgAdmin, LocAdmin and more)
Switch back to the Testserver website test.cacert.org and continue testing

People interested in helping CAcert can become tester
All you need to know is, how can I access a website
To become a tester you can contact
- The Software-Assessors team (see Software#Software-Assessment)
- The Software-Assessment Project team (see Software/Assessment)

Reporting is the main issue on testing
Test reports have to be added into the Bugs.cacert.org under the bug# of the tested patch
On the Testers Entry page, the list of current patches are listed, each with a bug# and a link to bugs.cacert.org
If you don't have an account yet on bugs.cacert.org, its now time to add a new account
Open the bug# page and add a note for reporting
- if you have found no errors, describe in short the tests you've did and in summary, that you didn't find an error
- if you have found an error, describe the error that persists and the steps for reproduction

If you don't have an account yet on bugs.cacert.org, its now time to add a new account
if you have found an error that doesn't relate to the patch you are testing, add a new bugreport
- add links to the new bug# for the patch you are tested and under the bug# of the patch you have tested, add the new bugs# so developers can decide, if they'll fix the new found bug with the current patch

There is a Testserver Image available (QEMU) that you can use to run on your own machine.
- This Image includes the locations database set
- Ask Philipp for the link
The new Testserver built is also available for download
- The links can be found on page SystemAdministration/Systems/Development at the bottom