Manual System Testing Instructions

[imnasnainaec]

We want to cover as much of The Combine as we can with unit testing and CI, but it might be worth having a set of procedures for manually testing the app's functionality.

Update: Some BVT/regression testing covered in https://github.com/ubsicap/TestAutomation/tree/master/CombineWebTests

[johnthagen]

A user created tutorial that talks about some of the feature they are using: https://tutorials.canil.ca/thecombine

I would suggest a simple format for the system tests (probably in docs/system_tests as Markdown). It would err on the side of being concise since this will be need to updated as the app evolves. I think a concise up-to-date set of tests would be more useful that a super verbose set that devs are reluctant to maintain.

Test Category (e.g. Login, Audio etc)

Test Name (User Login)

1. Step 1
   • Expected outcome if needed
2. Step 2
3. Step 3

[johnthagen]

This would also be a great thing to add as part of the release process.

[imnasnainaec]

I'm meeting with Don Dillard to initiate systematic Test Case Development.

[johnthagen]

Might be worth exploring: https://github.com/mherrmann/selenium-python-helium

This could be a way to write very concise automated web tests.

[johnthagen]

A plug to remember to add tests for the email functionality as I suspect these are rarely tested on developer machines due to needing credentials and an active server and real email addresses.

[johnthagen]

Given #1123 was just found, I think this increases the importance of system testing the email features.