Please enable JavaScript.
Coggle requires JavaScript to display documents.
TEST DESIGN TECHNIQUES - Coggle Diagram
TEST DESIGN TECHNIQUES
Black-box testing techniques
Boundary Value Analysis
Equivalence Partitioning
Decision Tables
State Transition
Use Case Testing
Static testing techniques
Most static techniques can be used to test any form of documents (Source code, Design documents,....)
Help engineers to recognize and fix their own defect in the early stages in the development process
Static techniques won't solve all problems, but very effective. Improve quality and productivity.
IDENTIFYING TEST CONDITIONS AND DESIGNING TEST CASES
Test condition
Specifying test cases
Basically, test design is the act of creating and writing test suites for a software
When we come to make a test case, we are required to be specific
Test cases can be documented with
"IEEE 829 STANDARD"
Test cases check that system does what it is supposed todo
Give us generic idea for testing which covers quite a large range of possibilities
Test implementation: specifying test procedures or scripts
The document that describes the steps to be taken in running a set of tests is called a test procedure, and is often also referred to as a test script.
Automation script
Written in a programming language that the tool can interpret.
Manual script
For tests that are intended to be run manually rather than using a test execution tool.
Formality of test document
Formal testing would have extensive documentation which is well-controlled
Informal testing may have no documentation
The right level of formality for you depends on your context
The level of formality is also influenced by your organization - the culture
Pros and cons of document
Pros
Reduce or eliminate some uncertainty about test operation
Is a resources for newbie testers
Cons
Time-consuming
Keeping track of the changes requested by the client and updating the documentation accordingly is quite tiring
Test analysis: identifying test conditions
Test analysis is the process of looking at something that can be used to derive test information. This basis for tests is called 'test basis'
Test condition is simply something that we could test
Test possibilities is a list of test conditions
Test techniques is techniques for filtering some test conditions to separate into many sub-list of test possibilities
Test conditions should link to their sources in test basis - called traceability
Prioritizing test conditions is an important thing to do after identifying test conditions
Test data should be designed to represent the most important types of data
Introduction
Test condition
Are documented in a Test Design Specification
Test cases
Are documented in a Test Case Specification
Test procedures
Are documented in a Test Procedure specification
White-box testing techniques
White box testing is a code-based testing technique in which the internal structure is being known to the tester who is going to test the software.
White box testing involves the testing of the software code for the following
Internal security holes
Broken or poorly structured paths in the coding processes
The flow of specific inputs through the code
Expected output
Testing of each statement, object, and function on an individual basis
Advantages and Disadvantages of White-box Testing
Advantages
Code optimization by finding hidden errors.
White box tests cases can be easily automated.
Testing is more thorough as all code paths are usually covered.
Testing can start early in SDLC even if GUI is not available.
Disadvantages
White box testing can be quite complex and expensive.
Developers who usually execute white box test cases detest it. The white box testing by developers is not detailed can lead to production errors.
White box testing requires professional resources, with a detailed understanding of programming and implementation.
White-box testing is time-consuming, bigger programming applications take the time to test fully.