What to learn in testing

Drop a taxi test Supervisor problem summary;

The test is divided into three main categories: app testing, Web testing, application testing (currently the most app testing, web second, the least application);

App testing focuses on networking, app launch, app compatibility, UI testing, interface testing, and performance testing.

Web testing focuses on UI testing, interface testing, and performance testing;

Need to prepare for

Common test methods (white box test, black box test, pressure test, etc.);

Know what an equivalence class

Basic SQL, you need to know how to view the data during testing

Python, can write automated test cases

Know some simple Linux instructions that will look at the log

Ability to read simple Java programs

Learn about the LoadRunner and SOAPUI performance testing tools

will use the Grab Kit tool fiddler and Charles

The basic algorithm, the test paper and the development of the same

Test questions:

Differences between black-box, white-box, unit, integration, system, and acceptance tests

black Box Test : The functional design specifications of a known product can be tested to verify that each implemented function meets the requirements.

White Box Testing : The internal working process of a known product can be tested to prove that each internal operation complies with the design specifications and that all internal components are inspected.

The black box test of the software means that the test should be done at the interface of the software. This method is to see the test object as a black box, the tester does not consider the internal logic structure and internal characteristics of the program, only according to the requirements of the program specification, check the function of the program is consistent with its function description . So black-box testing is also called functional testing or data-driven testing .

The black box test is mainly to find the following types of errors:

1. Are there any features that are incorrect or missing?

2, on the interface, the input can be correctly accepted? Can I output the correct results?

3. Are there any data structure errors or external information (such as data file) access errors?

4, performance can meet the requirements?

5. Are there any initialization or termination errors?

1 ) function error or omission;

2 ) interface error;

3 ) data structure or external database access error;

4 ) performance error;

5 ) initialization and termination errors.

The software's white-box test is a detailed examination of the procedural details of the software. This approach is to think of the test object as an open box, which allows the tester to design or select test Cases and test all the logical paths of the program, using the logical structure within the program and related information. Determine whether the actual state is consistent with the expected state by checking the program state at different points. So white-box testing is also known as structural testing or logic-driven testing .

White box testing is mainly to the program module to check the following:

1, test all the independent execution path of the program module at least once.

2, to all the logical judgment, take "true" and take "false" two cases can be measured at least once.

3. The loop body is executed within the boundaries of the loop and the boundary of the operation.

4, test the effectiveness of internal data structure, and so on.

Unit Testing (module testing) is a small piece of code written by a developer to verify that a small, well-defined function of the code being tested is correct. Typically, a unit test is used to determine the behavior of a particular function under a particular condition (or scenario).

Unit testing is done by the programmer himself, and ultimately the programmer himself. It can be said that programmers have the responsibility to write functional code, but also have the responsibility for their own code to write unit tests. Performing unit tests is to prove that the code behaves as we expect it to.

The primary purpose of unit testing is to address various errors that may exist during the encoding process, such as errors in user input boundary values during validation.

Integration Testing (also called assembly testing, joint testing) is a logical extension of unit testing. Its simplest form is: Two tested units are assembled into one component, and the interfaces between them are tested. In this sense, a component refers to an integrated aggregation of multiple cells. In a real-world scenario, many units are assembled into components that are then assembled into a larger part of the program. The method is to test the combination of fragments and eventually extend the process to test your module with the other group's modules. Finally, all modules that make up the process are tested together.

The main purpose of integration testing is to address possible problems in detailed design, especially to check for possible errors on interfaces between units and other program parts.

The system test is to assemble the tested subsystem into a complete system for testing. It is an effective method for verifying that the system is indeed able to provide the specified function in the system scheme specification. (Common test of joint adjustment)

The purpose of the system testing is to thoroughly test the final software system to ensure that the final software system meets the product requirements and follows the system design.

System testing is primarily designed to check whether the system is effectively functioning as a whole, such as whether the expected high performance is achieved in the product setup.

The acceptance Test is the last Test action before the software is deployed. The purpose of the acceptance test is to ensure that the software is ready and that it can be used by end users to perform the established functions and tasks of the software. Acceptance testing is to show future users that the system can work as expected. After integration testing, has been designed to assemble all the modules into a complete software system, interface errors have been basically excluded, and then should further verify the effectiveness of the software, which is the task of acceptance testing, that is, the function and performance of the software as the user reasonably expect.

Acceptance testing is usually performed by a business expert or user to verify that the product is truly in line with the needs of the user's business.

to design a complete test case :

1, familiar with business needs.

2. Design test cases on the basis of familiar requirements.

3. Design normal business test cases

4. Design abnormal condition test case.

Test case design method for black box test

• Equivalence class Partitioning method

• Boundary value Analysis method

• Error-guessing methods

• Causality Diagram method

• Decision table Driven analysis method

• Orthogonal experimental Design method

• Function Diagram Analysis method

4. Common function test methods:

1. Page link check: Each link has a corresponding page, and the page between the correct switch.

2. Correlation check: the deletion/addition of an item will have an impact on other items, and if so, whether the effects are correct.

3. Check the function of the button is correct: such as update, Cancel, delete, save and other functions are correct.

4. String length check: Enter the length of the string beyond what is required, and see if the system checks the length of the string for errors.

5. Character type check: Enter other types of content where the content of the specified type should be entered (for example, enter a different character type where the integer type should be entered) to see if the system checks the character type and whether it will error.

6. Punctuation check: The input includes various punctuation marks, especially spaces, various quotes, and enter. See if the system is working correctly.

7. Chinese characters processing: In the system can input Chinese language, see if there will be garbled or error.

8. Check the integrity of the information that is brought out: when viewing the information and update information, check that the information you have filled out is not all taken out., bring out the information and add the consistency

9. Information duplication: In some need to name, and the name should be the only information to enter a duplicate name or ID, see if the system has been processed, will be error, the name includes whether it is case-sensitive, and the input before and after the input space, the system to make the correct processing.

10. Check the deletion function: In some places can delete more than one message at a time, do not select any information, press "delete" to see how the system processing, will be wrong; then select one and more information, to delete, to see if the correct processing.

11. Check that additions and modifications are consistent: Check that the requirements for adding and modifying information are consistent, such as adding required items, modifications should also be required, adding items that are defined as integral types, and modifications must be integral.

12. Check the name of the change: The changes can not duplicate the name of the item to the existing content, to see whether the processing, error. At the same time, also pay attention to, will be reported and their name of the wrong.

13. Repeat the form: A record that has been successfully submitted, and then submit it back to see if the system has been processed.

14. Check the use of the back key in the situation: in the place where you have to return to the original page, and then to repeat, to see if there are any errors.

Search Check: Enter the contents of the system where there is a search function, and see if the search results are correct. If you can enter multiple search conditions, you can add both reasonable and unreasonable conditions to see if the system is working correctly.

16. Enter the information location: note When you enter information where the cursor is resting, the cursor and the information you enter will be skipped elsewhere.

17. Upload the download file check: Upload the download file function is implemented, upload file can open. What is the format of the uploaded file, whether the system has the explanation information, and check whether the system can do it.

18. Required fields check: Should fill in the item is not filled out when the system has been processed, the required fields are prompted for information, such as the required fields before adding *

19. Shortcut key check: whether to support common shortcut keys, such as CTRL C CTRL V BACKSPACE, etc., for some fields that do not allow input information, such as the selection of the date of the shortcut is also limited.

20. Enter Check: Press ENTER after the end of the input to see how the system processing, will be error. Hello, welcome to the joint discussion! Have time to visit it labs, every day software testing network

http://blog.csdn.net/koudaidai/article/details/7394126

5, how to understand the pressure, load, performance test test?

Performance testing is a large scope, in fact, the performance test itself contains performance, strength, pressure, load and other aspects of the test content.

Stress Testing is a common test for the stability of the server and the load capacity. Increasing the number of users accessing the system, or a few users doing large data volumes, is a stress test.

The load test is a relatively large pressure test, which is the corresponding ability of the test system under one or the concentrated limit condition, and is an important part of the performance test. 100 users of the system for a continuous half-hour access can be seen as a stress test, then continuous access to 8 hours can be considered load test, 1000 users continuous access to the system 1 hours can also be seen as a load test.

There is actually no obvious distinction between stress tests and load tests. Testers should be able to test the system at a height that focuses on overall performance

6, what is the system bottleneck?

bottleneck is mainly refers to the whole software and hardware composed of a certain aspect or several aspects of the ability can not meet the specific business requirements of users, "specific" means that the bottleneck will occur under certain conditions, because most systems before the input.

Technically, all systems have bottlenecks, because most systems are not coordinated, for example, when CPU usage reaches just 100%, the memory is just running out of the system. Therefore, we discuss the system bottleneck from the perspective of application: The key is to see whether the system can meet user needs. In the case of user limit system, the response of the system is still normal, we can think that the system without bottlenecks or bottlenecks will not affect the user's work.

So our test system bottleneck is mainly for the following two purposes:

- Discover the "surface" bottlenecks . The main purpose is to simulate the user's operation, to find out the bottleneck of user limit using system, and then solve the bottleneck, which is the basic goal of performance testing.

- identify potential bottlenecks and resolve them to ensure long-term stability of the system. The main consideration is that the system can adapt to the change when the user expands the system or the business changes in the future. The system that satisfies the user's current needs is not the best, the goal of our design system is to ensure that the whole software life cycle of the system can adapt to the changes of the user, or can adapt to the new changes by simply expanding the system.

What to learn in testing