We use TeamCity to auto-run our tests and keep record of results. Ask QA team if a test needs to be added/muted/ignored. Every time when a new build is started, a thorough run of tests is pended. (you can view all pending and running jobs in TeamCity)
Here is code style guidelines document:
/wiki/spaces/QAT/pages/5432088662
Current scripts structure:
PS_APINightly_test: (tests that run periodically in TeamCity)
template tests:
- Certificate Templates (compile and render the template)
- Notification Templates (compile and render the template)
- NavPage Templates (compile only since render is hard to test for now)user importer tests: (each organization may have unique user importer setup, so we need to test them separately)
- BCF user importer
- CMG user importer
- CCL user importer
- Default user importer
PS_Functional_test: (tests that manually run)
Render certificate templates in browser (note: the template resources cannot be loaded automatically for now)
Tips:
Avoid “directly“ execute command (using script like
root.API.executeCmd("")) in script page (i.e. notificationTemplates_test.py), since the command in system can be modified. Create a function to execute command. Collect all functions in a file in folder MarineLMS.Test.QA. (i.e. Template.py is a collection of all functions needed by template test script)Try to organize your test objects as classes. It helps you to protect data, manage you test steps and clean up after testing. (i.e. files in MarineLMS.Test.QA/LMSClasses)