Static testing studied in this chapter, refers to component or system testing at specification or implementation level.
There is no execution of the software, only code or document review in static testing before dynamic testing.
LO-3.1.1 Recognize software work products that can be examined by the different static techniques (K1)
Work products are manually reviewed and commented, these could be:
- requirements specifications, design specifications: aims is to find omission, ambiguity, inconsistency.
- code: aim is to find inefficiencies and resolve them before the product may be delivered.
LO-3.1.2 Describe the importance and value of considering static techniques for the assessment of software work products (K2)
Early testing is the principle on which static testing is based on for conducting manual reviews and evaluation of the product before the design of the software. (requirements, specifications). Moreover we saw in the previous posts about testing principles that defects found earlier in the project lifecyle are cheaper to fix.
Static testing contributes then to this anticipation, it removes defects which could be found later when dynamic testing is performed and reduces testing time and cost.
LO-3.1.3 Explain the difference between static and dynamic techniques, considering objectives, types of defects to be identified, and the role of these techniques within the software life cycle (K2)
Dynamic and static testing are complementary and have the same objective which is identify defects.
Teams have to work together, static testing can be performed incrementally for raising issues which are likely to be deviations from standards or requirements initially agreed with the stakeholders, and this before dynamic testing by verification/validation is performed.
Thank you for the nice article here. Really nice and keep update to explore more gaming tips and ideas.
ReplyDeleteGame Testing
Video Game QA
IOS Game QA Testing Services
Game Performance Testing
Quality Assurance Games