Explain the relationships between software development activities and test activities in the software development lifecycle

Regardless of the development model, there are several principles of good testing:

Explain the difference between the mindset required for test activities and the mindset required for development activities

The thinking of the tester and the developer has significant differences.

The main task of a developer is to design and create products. Therefore, the developer is more busy thinking through the creation of the product, rather than analyzing why it may not work.

Identify the psychological factors that influence the success of testing

The identification of defects at different stages of product development can be perceived as a criticism of the product and the author's personality. Creators are often convinced of the correctness of their projects and code, and therefore may perceive the tester as a person who creates problems, and not as a person who works to improve their product. Therefore, in the past, it happened when the messenger who brought bad news was simply executed.

Explain the value of maintaining traceability between the test basis and test work products

Traceability allows to monitor the relationship between each element of the test basis and the corresponding work products throughout the testing process.

Differentiate the work products that support the test process

Test planning work products

Mainly, products for planning test activities include one or more test plans. The test plan includes information about the test basis to which other test work products will be related through traceability information, as well as the exit criteria that will be used during testing. monitoring and control.

Describe the test activities and respective tasks within the test process

A testing process consists of the following main activity groups: test planning, test monitoring and control, test analysis, test design, test implementation, test execution, test completion. Each activity consists of different tasks that can change from one project to another.

Explain the impact of context on the test process

There is no universal test process. 

The content of the testing process depends on many factors, that is, it depends on the context of its implementation. 

Explain the seven testing principles

1. Testing shows the presence of defects, not their absence

Each test checks the program for compliance with specific specified conditions. Therefore, the test can only detect defects that appear only with the parameters specified in the test. Since a finite number of tests are used, it is therefore impossible to establish the absence of defects in the software.

Distinguish between the root cause of a defect and its effects

All defects have their root causes, i.e. the conditions and / or earlier actions that led to the defect.

Therefore, the search for the root causes and their analysis is the key to a significant reduction in the number of defects provoked by them in the future.

Distinguish between error, defect, and failure

People make mistakes (errors), and they can lead to defects in documentation and software. At the same time, an error in one work product may lead to an error in another work product that related with the first work product.

Describe the relationship between testing and quality assurance and give examples of how testing contributes to higher quality

Quality assurance and testing are not the same thing, but they are interrelated.

Quality management includes quality assurance and quality control.

Give examples of why testing is necessary

All people periodically make mistakes, so software products also contain defects, as a result of this. However, the use of appropriate testing techniques by qualified testers can reduce their number:

Differentiate testing from debugging

Testing and debugging are not the same process.

What is Testing? Identify typical objectives of testing

The typical objectives of testing are:

- Evaluation of work products such as requirements, user stories, design, and code

- Verification if all specified requirements are met