I am trying to establish more formal requirements and testing procedures than now, but I can not find good reference examples of documents.
At the moment, after the click-to-test property testers before deployment, there is no formal specification of what to test.
Firstly, I am thinking of a document that defines every function that needs to be tested, something like this (creating this):
- user registration form
- drop-down list of countries (are countries selected from the server correctly?)
- password verification (are all password rules followed, is the user notified if the password is too weak?)
- thanks in exchange for registration
... etc. It can also serve as a point for the client to sign as part of the requirements before programmers begin coding. After the list of functions is completed, I'm going to make this list the first column in the spreadsheet, which also says when the last function was checked, it worked, and if it did not work, how it broke. This would give me document testers that could be filled after each testing cycle, so that programmers have a to-do list, with information about what does not work and when it broke.
Secondly, I am thinking of test cases for testers, with detailed steps, for example:
- Download the user registration form.
- (Feature 1.1) Check the country drop-down menu.
- Is a country dumped by country with country?
- Are country names localized?
- ?
- ( 1.2) : "a", "bob", "password", "password123", "password123 #". .
- "".
- ( 2) .
, , . ( , ).
, , . , . , , , , .
, Word/Excel. /bugfixing . , (JIRA), . , :
- PM . . ( 1.)
- . ( 2.)
- .
- . ( 1.)
- .
- GOTO 4, .
- ; .
- , ? , , , .:)