Portal system testing-Test Plan 01/29 Update SLTechnology News&Howtos

Portal system testing-Test Plan

2025-01-29 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Internet Technology >

Shulou(Shulou.com)06/03 Report--

1 Overview of Test Plan 1.1

The purpose of the test plan is to test whether the functions implemented by the system meet the requirements defined in the requirements phase, whether the performance meets the needs of users, and whether the security has the security level that the enterprise application system should have. The reading objects include:

-system requirements researcher.

-system designer.

-system developers.

-system end user or end user representative.

-relevant project managers.

The functional tests included in the test plan are:

-Unit testing.

-Integration testing.

-system testing.

-acceptance testing.

The non-functional tests included in the test plan are:

-performance testing.

-Safety testing.

According to the system requirements specification, list the main functional modules of the system, the functional point list of each functional module, the business scenarios and software system operation scenarios included in each functional list, the use cases included in each scenario, and each use case must list in detail the specific operation steps, input values and output values of each step, in which the output value is only the expected output value (Expected Result) in the plan. However, the actual output value (Actually Result) must be written in the test report.

When writing test cases, you must make a list of all the use cases and define the priority of the test cases after each list. The priority of test cases is as follows:

Hmure-must be tested.

Mmurf-should be tested, only after all H items have been tested.

Lmurf-it may be tested, only after all H and M items have been tested.

(1) performance testing

According to the system requirements specification, determine the main business scenarios, secondary business scenarios, the test cases contained in each scenario, and the frequency of each test case. In the test plan book, we must design the test cases to be recorded, define the frequency of each test case, then combine to generate test scenarios, run these test scenarios automatically with the help of automated testing tools, and analyze the test results. until the required performance data is reached.

(2) Safety testing

Design * sex test scripts to avoid security problems such as password-free login, incorrect password login, URL path vulnerabilities, SQL injection vulnerabilities, and so on.

(3) user interface testing

The system end user tests whether the system interface is acceptable.

(4) regression test

Do a regression test where something went wrong with the test until the problem no longer occurs.

1.2 Test Resources

You must develop a detailed test plan before testing, and then follow the test plan step by step. The test plan involves the organization of testers, the preparation of system resources, the construction of test environment and so on.

1.2.1 Human Resources

The test plan must identify test managers, business test engineers, and IT test engineers, including the various roles that need to be involved in testing at each stage, as well as related responsibilities and permissions (see Table 1-1).

Table 1-1 Human resources required to test the project

Corner color

Number of people

Have a professional responsibility

Test Manager

One from both Party An and Party B

Responsible for test planning, preparation, organization and acceptance

Business Test engineer

Not less than 3

Mainly responsible for functional testing, testing whether the functions of the system meet the business requirements

IT Test engineer

Not less than 3

Mainly responsible for performance testing and safety testing, responsible for testing whether the non-functional indicators of the system meet the requirements

1.2.2 system resources

Table 1-2 lists the system resources required for the test project, including software and hardware resources, testing tools, and so on.

Table 1-2 system resources required to test the project

Resource name / Type

Basic configuration and quantity

PC desktop

Minimum configuration: P4, main frequency 1.6GHz or above, hard disk 40GB, memory 512MB, 5 sets

systems software

Microsoft IE 7.0 and above

Application softwar

Microsoft Office 、 Visio

Test management platform

A test management platform must be built.

Performance testing tool

LoadRunner 8.0

1.3 Test environment

Users' environmental requirements when running the system, such as the required operating system, software version, and other special environmental requirements, can consider whether this section is needed according to different project characteristics and actual conditions.

It is not advisable to use the same user ID to simulate multiple concurrent implementations. Here, you need to provide 100 pairs of real user names and passwords, which are stored in the file userinfo.dat for use in the test scenario. 100 real users simulate 300 concurrency, which is designed as a fault-tolerant test to a certain extent. That is, the same ID carries out concurrent multi-resource operations at the same time, and even some ID have exited the system.

1.4 Test implementation phase

When you develop a test plan, you must also indicate the tests to be performed at each phase, and Table 1-3 shows at which stage the tests will be executed.

Table 1-3 Test execution phase

Test type

Test phase

Unit testing

Integration testing

System testing

Acceptance test

Function test

√

Performance testing

(X) optional, or when defects are found in the system performance test

√

Safety testing

(x) optional

User interface testing

(x) optional

√

regression testing

Regression testing is performed at the appropriate testing phase when the software being tested or its environment changes

1.5 Test progress

The test plan must include a detailed test plan, and figure 1-1 shows the test schedule developed by a project.

Figure 1-1 Test schedule

The specific test time plan is shown in Table 1-4.

Table 1-4 specific test schedule

Test phase

Start time

Completion time

Executive staff

Phase completion flag

Develop a test plan

2011-07-12

2011-8-01