2. A developer aims to be an optimist by the outcome of the
code/program.
BUT…
A quality assurance tends to be an pessimist when it comes
to the outcome of the code.
QA have to be a natural pessimist.
3. A QA engineer needs to ask questions in terms of search
contextually what the software is supposed to do and what it
doesn't need to do.
At the same time, follows through by executing scenarios in
order to check those parameters.
Types of check:
Boundary | Requirements | Condition
4. In order to be effective, there is a need to be curious.
You should be the one who does not conform to the norm
but the one who looks into what other areas that needs to
be explored.
6. i. Review the test cases
Done by:
stakeholders | manager | development team
requirements engr.| quality engr.
ii. Check integration testing
iii. Do exploratory testing
7. Exploratory testing means we have to live by what the
software needs.
The plainest definition of exploratory testing is test design
and test execution at the same time.
For example, if we're doing a housewife, we have to feel
what is to be one and what is its functionalities.
8. Testing are incorporated in every part of the development of
the software:
agile testing | sanity testing | exploratory testing
integration testing| requirements checking
During the development we take time on executing those
testing mentioned.
