Class Notes (V)

System Testing

• definition

System testing--is an integrated software systems, as an element of the entire computer system, and computer hardware, peripherals, some supporting software, data and personnel and other system elements together in the actual operation of the environment, the computer system to carry out a series of testing activities;

• Object

1. Product level--software + hardware

2. Project-level-software (may also contain hardware)

• completeness

How to ensure the completeness of the system testing?

1. There is a test case for all requirements as far as possible;

2. According to the quality characteristics of the software, to different angles, testing requirements;

3. According to different test case, methods, the construction of different testing data and processing process;

Common test methods

1.1 Functional Testing (function)

Custom

Function testing--verifies that the functionality of the product is implemented and meets the product requirements specification based on the SRS and test requirements list

Target

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

2. Is the function implemented to meet the needs of users and the implicit requirements of system design?

3. Can the input be accepted correctly? Can I output the results correctly?

1.2 Performance testing (efficiency)

Custom

Performance testing--tests the performance of the software in an integrated system. (mostly using tool testing)

Target

Measure the difference between a system relative to a predefined target.

Implementation

1. The performance indicators are clearly defined.

2. Structural performance Test Research data.

3. Construct different performance test scenarios.

4. Perform performance tests (General >90% on).

5. Performance analysis.

6. Performance fault location.

7. Performance optimization.

• Based on

1. Resource occupancy.

2.CPU response time.

Difference

1. Stress test-do not stress the amount of pressure, only check the conditions of pressure.

2. Capacity testing-stress and pressure.

3. Performance test-after pressure test performance indicators to meet the requirements of resource use and response time.

1.2.1 Resources (Resource usage)

CPU Use cases.

io Use cases.

• Memory usage.

• Channel use things.

1.2.2 Time aspect (CPU response time)

• Percentage of execution time per module.

• A module waits for the percentage of Io to complete.

• Trace paths over time.

• The number of times each set of instruction pages is swapped in and out.

• The system reflects the time.

• System throughput, which is the number of processes per unit.

• Unit execution time for all major directives.

1.3 Pressure test/limit test (reliability)

Custom

The Stress testing--system behaves in a situation where its resources are ultra-compliant.

Target

In the extreme or harsh environment, the system's self-protection ability. The main verification system reliability.

Implementation

1. At the same time, a large number of users logged in.

2. Introduce a large number of operations.

Purpose

1. Is there a memory leak?

2. Verify system reliability.

3. Give the user a clear definition after testing.

Difference

1. Stress test-do not stress the amount of pressure, only check the conditions of pressure.

2. Capacity testing-stress and pressure.

3. Performance test-after pressure test performance indicators to meet the requirements of resource use and response time.

1.4 Capacity Testing

Custom

The volume testing--enables the system to withstand excess data capacity to see if it can handle it correctly.

Target

1. Test whether the system capacity meets the requirements of the system capacity.

2. If the system capacity is not specified, a clear capacity definition can be given through this test.

Implementation

1. Construct a batch of large-capacity test data input to the system.

2. The whole system structure of different business scenarios, repeated execution.

Difference

1. Stress test-do not stress the amount of pressure, only check the conditions of pressure.

2. Capacity testing-stress and pressure.

3. Performance test-after pressure test performance indicators to meet the requirements of resource use and response time.

1.5 Security Testing (features)

Custom

The security testing--verifies that the protection mechanism integrated in the system can protect the system from unauthorized intrusion in practical applications.

Purpose

Ensure system security, data integrity, confidentiality.

1.5.1 Data

Integrity

• The integrity of the data store.

• Integrity of data confidentiality.

Confidentiality

• Confidentiality of data storage.

• Confidentiality of data access.

1.5.2 Permissions

• Assignment of permissions

• Use of permissions

1.5.3 protocol

More in mobile phone testing to use.

1.5.4 Other

such as log..

1.6 GUI test (easy to use)

Custom

Graphical User Interface testing--test for the interface of the software system.

Target

1. Interface implementation and interface design in accordance with the situation. (Interface Design)

2. Confirm the correctness of the interface processing. (for different control analysis)

• Related automated testing tools

1.WinRunner

2.SilkTest

3.QaRun

1.6.1 Simple interface elements

Custom

A single interface area where functions and attributes are relatively simple, that is, the various controls commonly referred to.

Method

The main concern is their appearance, performance behavior.

1.6.2 Combined class interface elements

Custom

Some complex interface elements, such as tables, various text editors, and so on.

Method

It is decomposed into simple interface elements before being processed.

1.6.3 full Interface (window)

Custom

The interface form, which is composed of a series of interface elements through appropriate forms, is the most common for various windows. Includes various dialog boxes, single document windows, multiple document windows, multiple windows, etc.

Method

Appearance, layout, behavior.

1. Input class interface elements: With regard to its appearance, the characteristics of input such as echo, alignment principle, scrolling principle and so on.

2. Output class interface elements: Appearance.

1.7 Usability testing (ease of use)

Custom

Usability testing--How good it is to detect the user's understanding and use of the system.

Target

1. Consider whether the product conforms to the actual application situation.

2. Whether it conforms to user's custom or special requirements.

3. Whether the operation is convenient and reasonable, the equipment and users see whether the interactive information is accurate and easy to understand, whether to comply with industry habits, appearance/interface is beautiful and so on.

• General concerns about usability issues:

1. Overly complex functions or instructions.

2. Difficult installation process.

3. The error message is too simple.

4. Users are forced to remember too much information.

5. Syntax, format, and definition are inconsistent.

1.8 Installation Test

Custom

According to the software test features list, software installation, configuration documentation, design the installation process test cases, found the software during the installation process errors.

• Subjects to be tested:

1. The software itself.

2. Software Installation documentation.

1.8.1 the work to check before installing the test

1. The installation documentation is complete.

2. The program files for installing the software are complete.

3. The installed files of the tested software are complete.

4. The Software Installation documentation is complete.

5. Check that the file format of the software matches the file format required in the installation instructions documentation.

1.8.2 work during installation testing

1. All the preset data is complete.

2. The software environment configuration is reasonable.

3. The hardware environment configuration is reasonable.

4. The set of options selected by the user is compatible. ¦

5. During the installation process:

A. The system provides default parameter values for installation testing.

B. Specify that the installation process is completed manually, list the work required for each step of the installation, and carefully review the correctness of the work done by each installation step.

C. Install test cases for which you want to design exceptions during installation testing, including exceptions to configuration parameters, installation options, and installation path exceptions.

6. Test the installation documentation.

1.8.3 inspection work to be done after installation

1. All documents have been produced and have the necessary content.

A. The directory of the program files is correctly generated.

B. Whether the program files under each directory and sub-directory are correctly generated.

C. Whether there are useless directories, subdirectories, program files, and useless subdirectories.

D. The permissions of the directory, subdirectories, and program files themselves are correct.

E. For Windows also check the dynamic link library files that are compatible with the application software.

2. Check the installation log.

3. After the installation is complete, the program is run and the connection is verified.

4. Uninstall test of the software.

1.8.4 software upgrade test in installation test

1. The software is re-installed to achieve the purpose of upgrading.

2. The software upgrade is done by patch method.

3. Online upgrade.

1.9 Configuration Test

Custom

System in a variety of hardware and software configuration, different parameters configuration system has the function and performance.

Target

Verify the operability and validity of all configurations.

1.10 Anomaly Test/recoverability test (reliable)

Custom

Fault tolerance testing. It is an important means to evaluate the system reliability by means of artificial intervention, which can test the fault tolerance and recovery ability of the system.

• Exception Handling

1. The system is processed automatically.

2. Manual intervention Treatment.

• Note

1. The system anomaly is also related to the system's indicator test, when the system's service capability is larger than the system design index, it also belongs to the abnormal situation of the system.

2. The reliability of the system is designed, not tested. The data tested helps to accumulate experience in our further system optimization design and testing is a process of mutual feedback.

1.11 Backup test (reliable)

A supplement to a restorative test that verifies the ability of a software or hardware failure to back up his data.

1.12 Robustness Test (reliable)

The robustness testing is used to test whether the system can automatically recover or ignore failure to continue running in the case of a failure.

1.13 Document Testing

Documentation testing the correctness of the test documentation to ensure that the operation manual process is working properly.

1.14 Online Help Test

Online Help testing detect the reliability and correctness of the actual line.

1.15 Network Testing

network environment and other equipment docking, the system functions, performance and indicators of testing, to ensure the correctness of the docking.

1.16 Stability Test

The amount of time that can be sustained under certain load conditions.

2 system test test process

2.1 Planning Phase

Define what goals, why test objectives, when controllable time, where test scope, how to carry out. The main activities are: participate in the development of software requirements analysis, SRS review, through the post St plan, the St plan review.

• Ingress guidelines: SRS completes and determines the Requirement specification baseline

• Input: srs| sdp| SVVP

• Export guidelines: St Plan review passed

Output

2.2 Design phase

The main activities are: the organization personnel according to the test plan to write the test scheme, and the System plan review

• Entrance Guidelines: St Plan review passed

• Input: St Plan | Srs

• Export Guidelines: St Program Review passed

• Output: St Solution

2.3 Implementation Phase

The main activities are: organizing the test cases, test procedures and forecast items according to St program, and review them

• Entrance Guidelines: St Program Review passed

• Input: St Plan | srs| St Solution

• Export guidelines: Test cases, test procedures and predictive trial review

• Output: Test cases, test procedures, and predictive trials

2.4 Implementation Phase

The main activities are: Organization test execution activities, responsible for the defect report return to the development department to revise, organize test Report preparation, organize test report review

• Entry criteria: test cases, test procedures, and review of predictive trials

• Input: St Plan | St Solutions | St Use case | St Procedures | St Predictive test items

• Export Guidelines: St Report Review and adoption

• Output: St Pre-Test Report | St Test Report | Defect Report

Class Notes (V)