Timeline for How to properly test manually a web app
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 5, 2018 at 6:44 | answer | added | Ajay Balamurugadas | timeline score: 0 | |
| Jul 25, 2018 at 14:11 | vote | accept | John | ||
| Jul 25, 2018 at 13:46 | comment | added | John Burley | The test case you provided in your question is much easier to read than the Use case, this is good. You should have three more test cases to encapsulate the alternative scenarios. If you want formal testing then all known paths through the ‘Login page’ need to be documented in the test cases. A collection of small readable test cases are much better than one large test case covering the same testing area. | |
| Jul 25, 2018 at 13:35 | answer | added | John Burley | timeline score: 1 | |
| Jul 25, 2018 at 13:00 | answer | added | dvniel♦ | timeline score: 3 | |
| Jul 25, 2018 at 12:50 | review | First posts | |||
| Jul 25, 2018 at 13:16 | |||||
| Jul 25, 2018 at 12:49 | comment | added | John | Thanks, I dont have much experience with testing. So i was reading something about testing and about manual testing and I would like to know if is a ok approah write test cases and execute that test cases manually. So this was a question. Other question is because it seems that the use cases are similar to test cases, as I have in the question, so I dont know if is necessary to write test cases or just use the use cases. | |
| Jul 25, 2018 at 12:46 | comment | added | dvniel♦ | Are you asking if it's okay to derive test cases from use cases? | |
| Jul 25, 2018 at 12:42 | history | asked | John | CC BY-SA 4.0 |