A developer aims to be an optimist by the outcome of thecode/program.BUT…A quality assurance tends to be an pessimist when it comesto the outcome of the code.QA have to be a natural pessimist.
A QA engineer needs to ask questions in terms of searchcontextually what the software is supposed to do and what itdoesnt need to do.At the same time, follows through by executing scenarios inorder to check those parameters. Types of check: Boundary | Requirements | Condition
In order to be effective, there is a need to be curious.You should be the one who does not conform to the normbut the one who looks into what other areas that needs tobe explored.
i. Review the test cases Done by: stakeholders | manager | development team requirements engr.| quality engr.ii. Check integration testingiii. Do exploratory testing
Exploratory testing means we have to live by what thesoftware needs.The plainest definition of exploratory testing is test designand test execution at the same time.For example, if were doing a housewife, we have to feelwhat is to be one and what is its functionalities.
Testing are incorporated in every part of the development ofthe software: agile testing | sanity testing | exploratory testing integration testing| requirements checkingDuring the development we take time on executing thosetesting mentioned.