Defect bombing and beta testing

Exploitation Software TestingSoftware is accelerating WorkAn excellent way to make progress, helping you find out OthersSoftware defects that may be missed.

Another way to become an efficient tester is to leverage the power of others.

　　1. Let others test your software

1) LetOthersHuman inspection software helps to break down pesticide monsters;

2) people not only see different ones, but also test methods;

3) letting others help test helps eliminate irritabilityMood;

4) The Way To observe others' solutions to the problem isLearningNewTesting Technology.

It is easy for people to fall into the trap of wanting to test the software independently. Do not do this.

　　Ii. Test sharing

If possible, there are at least a few testers to test the software unless the software project is particularly small.

A common method is to swap test tasks in a certain period of time.

At least let others spend time reviewing equivalent division and test cases. They can provide new or different ideas for testing based on their own experience.

An interesting way to share a test task is to schedule a bug bombing (BASH ).

Defect bombing: within a period of time (usually several hours), the entire test team stops the specified regular test task and participates in the bombing.

In the defect bombing, select a specific area of the software, and All testers test this area or this set of features in a centralized manner.

The selection area may be where the Software defects are located, to see if there are more potential problems, or the area where the Software defects are suspected to exist.

Defects bombing can be used to determine whether common tests will omit Software defects and the quality of code writing.

Although there are many internal rules for selecting a region, the final use of defect bombing will allow many people to find Software defects from a specific software region.

The partner requesting assistance in finding Software defects is the product support or customer service team-they talk to the customer when the customer calls or asks questions via email.

Note: The most common call for assistance received by product support personnel may be usability problems. Many people who make calls only want to know how to use the software, so it is better to have the Product Support Team assist in testing early in design to identify and fix usability software defects.

　　III,Beta testing

Another common process for others to verify and validate the software is called beta testing ).

Beta testing is a term used to describe the external test process. In this process, the software is distributed to the selected potential customer groups so that they can use the software in the actual environment.

Beta testing is generally performed at the end of the product development cycle. Ideally, only confirm that the software is ready to be released to the actual customer.

Beta testing targets can be very broad, from identifying the user interface to finding Software defects that impressed the early use of news media reporting software to the final step.

The software tester wants the person who manages the beta test to know the purpose of the beta test.

Consider the following questions:

1) who is a beta tester?

2) How do I know that beta testers have used software?

3) beta testing can be a good way to find Software defects in configuration and compatibility;

4) usability testing is another area where beta testing can make a difference;

5) Apart from configuration, compatibility, and usability, beta testing is unexpectedly poor in looking for Software defects.

Note: attempting to use beta testing to replace actual testing is one of the main mistakes in software product development. Do not do this. If this is feasible, why does software design and programming not do so?

6) The beta testing program will consume a lot of time for the tester.

A common task for new testers is to work with Beta customers to help solve their problems, answer questions, and identify Software defects they find.

It has been confirmed that beta testing is a good way to regression independent and informative test data to the software, but it must be correctly defined and managed for effectiveness-it can be said that this also requires testing.

　　Iv. Outsourcing Testing

A common practice for many companies is to outsource or submit part of the testing work to other companies that are good at various aspects of software testing.

Configuration and compatibility tests are usually ideal for outsourcing testing. These tests generally require large-size testing laboratories with a large number of different combinations of hardware and software, and some personnel to manage them.

Localization testing is another example that is typically outsourced for testing. Unless you have a very large testing team, it is impossible to have testers with various languages that can understand product support.

As a beginner in testing, although it is not required to decide which testing tasks to outsource, if the outsourced testing is the software part you are responsible for testing, you need to work with the outsourcing company.

The success or failure of outsourcing tasks depends largely on the software tester. Consider:

1) What test tasks should the testing company consult? Who will define it? Who will approve it?

2) What progress do they follow? Who will set the progress? What if the deadline is exceeded?

3) What content does the testing company provide?

4) What content does the testing company provide? At least provide Software defects they have identified.

5) how to contact the testing company?

6) How do I know if the testing company meets the expectations? How do they know whether they meet their expectations?

The above issues are often ignored in the rush to outsource test tasks.

　　V. Summary

Use any method to make the test more effective.

1) it is decided to use technology;

2) requires additional personnel;

3) it is manually tested by brute force.

Each software test problem is unique and new knowledge can be learned during each test.

Reprinted: http://www.51testing.com/html/38/n-179538.html