White Box Test List

• Availability Testing
• Baseline testing
• Compatibility testing
• Compliance testing
• Configuration Testing
• Documentation testing
• Endurance testing
• Ergonomics Testing
• Interoperability Testing
• Installation Testing
• Load testing
• Localization testing and Internationalization testing
• Maintainability Testing
• Operational Readiness Testing
• Performance testing
• Recovery testing
• Reliability Testing
• Resilience testing
• Security testing
• Scalability testing
• Stress testing
• Usability testing
• Volume testing

LCSAJ Testing

LCSAJ testing requires a model of the source code which identifies control flow jumps (where control flow does not pass to a sequential statement). 

An LCSAJ (Linear Code Sequence and Jump) is defined by a triple, conventionally identified by line numbers in a source code listing: the start of the linear code sequence, the end of the linear code sequence, and the target line to which control flow is transferred.

ISTQB - Notes I

Common type of V-Model use 4 test levels
1- Component Test
2- Integration Test
3- System Test
4- Acceptance Test

V-Model can have different level of testing activity depends on project


--------------------------------------------------------

Typical tester tasks may include:
- Review and contribute to test plans.
- Analyze, review and assess user requirements, specifications and models for testability.
- Create test specifications.
- Set up the test environment (often coordinating with system administration and network
management).
- Prepare and acquire test data.
- Implement tests on all test levels, execute and log the tests, evaluate the results and
document the deviations from expected results.
- Use test administration or management tools and test monitoring tools as required.
- Automate tests (may be supported by a developer or a test automation expert).
- Measure performance of components and systems (if applicable).
- Review tests developed by others.

-------------------------------------------------------

Test approaches
- Preventative approaches, where tests are designed as early as possible.
- Reactive approaches, where test design comes after the software or system has been
produced.
-----------------------------------------------------------

State transition testing: A black box test design technique in which test cases are designed to
execute valid and invalid state transitions

---------------------------------------------------------------------------
Static testing: Testing of a component or system at specification or implementation level
without execution of that software, e.g. reviews or static code analysis.

--------------------------------------------------------------------------------------
Top-down testing: An incremental approach to integration testing

The process is repeated until the lowest level components have been tested

-----------------------------------------------------------------------------------