ROF: QA Test Conversation with Dave

To start:

1. Tester would probably start with ad-hoc testing first to get familiar

2. Then write test cases

Test cases:

1. Submit form with no info added - purpose: to get error / warning message

2. Test happy case / path - fill out with proper info and make sure it is saved correctly on the frontend, retrievable in whatever form (e.g. in table, on same page - if looked up later). Need to know what type of data you are testing for. One happy test case.

3. Test each field for the limits (e.g. numbers/special characters - in letter only field; enter a huge number in a field, if entering names; making sure app does not crash) - SQL injection- coded this - can add extra info or delete info (drop table command). Write user stories that have failures - e.g. enter special characters and get an error message.

4. If multi-page form, make sure it appears as needed (in another form or in a report or db)

5. Test for usability - language presented is understandable in FR and ENG; check for consistency, fields line up

6. Every field / function needs to be tested

7. Test what it interacts with - e.g. if needs to be populated in a report, then add to the test

Test access to a URL - cannot access pages they are not supposed to - eg. enter admin page URL, and test with role-based access.

Developers wrote automated tests based on what was written by the QA

Changes - automated software generates a test code, and then can update the test code. Then save and rerun the test code.