Testing is often referred to as test implementation, which means running software and testing. Test implementation includes the process of executing a program or application such as designing test or checking results, writing test reports, etc.
The main purpose of the Test includes the following steps
・Check the quality of the product
・Provide information to support product decisions, such as whether it has been released for example
・Prevent the creation of errors in the system
We need to distinguish the difference between Test and Debug. Test is to find errors, and Debug is to find out the cause of the errors and fix them. The responsibility of testing usually lies with testers, and the responsibility of debug belongs to the developers.
7 principles of testing
Principle 1: Testing can only prove that the software has errors
Through testing we can know that the software has errors, but can not prove that the software has absolutely no errors at all. Testing can reduce the number of errors in the software, but even in the absence of errors, we cannot claim that our software has no errors.
Principle 2: Testing the entire pattern is impossible
Testing the entire pattern (combining all conditions in data entry) is not possible, except for some extremely simple software. Instead of testing the whole thing, we should rely on risks or priority to focus on the points needed.
Principle 3: Test as soon as possible
To find bugs early, testing should start as soon as possible in the software development process.
Principle 4: The uneven distribution of errors
Most errors detected before releasing or during operation are concentrated in certain modules.
Principle 5: The principle of pesticides
When you perform the same test case multiple times, it will eventually fail to find the errors. To avoid this, it is necessary to review and improve test cases periodically.
Principle 6: Testing depends on conditions
For different conditions, there will be different test methods. For example, testing the banking system will be completely different from testing a sales website.
Principle 7: The “bug zero” pitfalls
Do not be too focused on creating a system without errors, but forget the initial requirements from customers.
The basic test phases
1. Planning and control
Test planning is the determination of the purpose of the test and the spec decision. Test control is the activity of comparing the plan with the progress during the test.
2.Test analysis and design
Convert abstract goals into specific test conditions or test designs. Specific example:
・Review for test base such as risk analysis report, interface spec, etc.
・Design test cases with their priority
・Classify the necessary test data
3. Test implement and Test execution
At this stage we will create scripts or test sequences based on test cases and other necessary information, then set up the environment and execute testing
4. Output and report evaluation
The output evaluation is the evaluation of whether the test implementation is satisfied with the purpose of the Test. For example:
・Compare Test results with specified Test end criteria at the Test Planning stage
・Judge whether you need additional tests or need to change the criteria for the output
・Write Test reports
Psychology of testing
Testers and Developers always have the same goal – to create a flawless solution for their client’s needs. But they work and think differently. If the developers have a suitable opinion then they can test it themselves. However, separating environment for the developers and testers will be more effective, and testing from a completely independent standpoint from development by well-trained pro testers will be more beneficial.
Tester is a reliable and objective third side that can see the possible mistakes and errors that Developer hasn’t predicted. While testing is a constructive job but it is sometimes considered negative so creating a good relationship between testers and developers is extremely important.
In order to build a good relationship between testers and developers, the following things are needed.
- There is a common goal of creating a good quality product, starting work with a cooperative attitude, not opposition.
- The opinions about the product must be neutral and true
- Try to understand the moods and reactions of others
- Try to convey what you want to say and understand what others want to say
For more information about Testing services, please contact us
Lotus Quality Assurance (LQA)
Tel: (+84) 24-6660-7474
Email: [email protected]