2024 Heilongjiang Vocational College Skills Competition and National Selection Competition "GZ034 Software Test" Competition Question Bank

2024 Heilongjiang Vocational College Skills Competition and National Competition Selection

"GZ0 34 Software Test " Competition Question Bank

Table of contents:

2024 Heilongjiang Vocational College Skills Competition and National Competition Selection

If you need competition information (guidance), you can send a private message to the blogger

"GZ034 Software Testing" competition question bank

Task 1: Functional testing (45 points)

Task 2: Automated testing (15 points)

Task 3: Performance Test (15 points)

Task 4: Unit Test (10 points)

Task 5: Interface testing (10 points)


Task 1 : Functional Test ( 4 5 points)

1. Test plan (5 points)

(1) Task description

For functional testing tasks, divide and define the testing scope, decompose testing tasks, and estimate testing risks, testing workload and testing progress. Complete this task according to the "A2-Test Plan Template".

(2) Task requirements

The test plan should include the following:

① Overview: Purpose of writing, project background.

② Test tasks: test purpose, test reference documents, test scope, test submission documents.

③ Test resources: software configuration, hardware configuration, human resource allocation.

④ Functional decomposition: Divide the overall functional modules.

⑤ Test arrangement.

⑥ Related risks.

(3) Task results

XX-A2-Test Plan.doc (XX represents the workstation number).

2. Test cases (15 points)

(1) Task description

Conduct demand analysis according to "A1-Requirement Specification", understand business functions, and design test cases. Complete this task according to "A3-Test Case Template".

(2) Task requirements

Test cases should include the following:

① Summarize the number of test cases by module;

② The test case should contain the following elements: module name, function items, use case description, preconditions, input, execution steps, expected results, importance, and test results of the execution case.

(3) Task results

XX-A3-Test Case.xls (XX represents the workstation number).

3. Bug list (20 points)

(1) Task description

According to the "A1-Requirements Specification" and test cases, perform functional testing, discover bugs, record bugs and take screenshots of bugs. Complete this task according to the "A4-Bug List Template".

(2) Task requirements

① The bug list should include the following:

Summarize the number of bugs by module and bug severity;

The bug list should contain the following elements: role, module name, function item, summary description, operation steps, expected results, actual results, defect severity, attachment description (screenshot).

② Use Google Chrome to perform web-side functional testing (including interface testing).

  1. Mission results

XX-A4-Bug list.xls (XX represents the work station number).

4. Test report (5 points)

(1) Task description

For functional tasks, analyze the overall test process, summarize the test results, and draw the final test conclusion. Complete this task according to the "A5-Test Report Template".

(2) Task requirements

The test report should include the following:

① Overview: Purpose of writing, project background.

②Personnel arrangement.

③ Test design: test case design methods and testing methods.

④ Use case summary: Use case summary.

⑤ Test review: progress review, functional test review.

⑥ Bug summary: Bug summary.

⑦ Test conclusion.

(3) Task results

XX-A5-Test report.doc (XX represents the work station number).

Task 2 : Automated testing ( 15 points)

1. Task description

Use Selenium methods to write automated test scripts and execute automated test scripts according to "A6-Automated Test Requirements". Complete this task according to "A7-Automated Test Report Template".

2. Task requirements

(1) The automated test report should include the following:

① Introduction: purpose, definition of terms;

② Automated test script writing: Topic 1, Topic 2, Topic 3, Topic 4.

(2) Tool requirements: Use PyCharm related environment to complete this task.

Note: During the process of running the automated test script, if an error occurs (the URL is entered incorrectly, the positioning element is not found, etc.), it is a script writing error. Please adjust it yourself; when writing the automated test script in PyCharm, single quotes, double quotes, brackets and It is important to write in English; when pasting the automated test script into the automated test report, it must be consistent with the script format in PyCharm. At the same time, do not paste all the code in one line or have a blank line when pasting.

3. Task results

XX-A7-Automated test report.doc (XX represents the work station number).

Task 3 : Performance Test ( 15 points)

1. Task description

According to "A8-Performance Test Requirements", use performance testing tools to record/add scripts, play back scripts, configure parameters, set scenarios and run to get results. Complete this task according to "A9-Performance Test Report Template".

2. Task requirements

(1) The performance test report should include the following contents:

① Introduction: purpose, definition of terms;

② Test strategy: test methods, use case design, test scenarios;

③ Performance test implementation process: performance test script design, performance test scenario design and scenario execution, performance test results;

④ Execution results.

(2) Tool requirements: Use LoadRunner and JMeter related environments to complete this task.

Note: 1. To open LoadRunner related software, you need to open it as an administrator. Any problems caused by not opening it as an administrator are the responsibility of the contestants; 2. During the performance test, recording failure, playback failure, and script execution failure occurred. White screen, 500 error, etc. are caused by performance testing tool usage or configuration errors. Please debug.

During the online competition, when the SwitchyOmega_Chromium browser plug-in is turned on, the system under test cannot be accessed directly through the URL. You need to open Fiddler and visit again to open the system under test and capture the packet successfully; after closing the plug-in, you can directly access the system under test through the URL. , but Fiddler cannot capture the packet. At the same time, due to VPN reasons, LoadRunner cannot record scripts directly. Fiddler packet capture results need to be saved and VuGen scripts generated for subsequent operations.

3. Task results

XX-A9-Performance test report.doc (XX represents the work station number).

Task 4 : Unit Test (10 points)

1. Task description

Carry out program design according to "A10-Unit Test Requirements", design test data, write unit test code, and complete compilation and program running in Eclipse. Complete this task according to "A11-Unit Test Report Template".

2. Task requirements

(1) The unit test report should include the following content:

① Program source code;

② Unit test code;

③ Screenshot of unit test results.

(2) Tool requirements: Use Eclipse related environment to complete this task.

Note: ① The number of all test data sets must be the minimum amount to meet the test requirements. ② During the unit test process, the default Workspace (cannot be changed) is used after starting Eclipse. You must create a new and complete relevant code design in test-src (JUnit, hamcrest-core, hamcrest-library and other jar packages have been imported into Referenced Libraries , if the contestants delete the jar package, they shall bear the consequences at their own risk).

3. Task results

XX-A11-Unit test report.doc (XX represents the workstation number).

Task 5 : Interface testing ( 10 points)

1. Task description

According to the "A12-Interface Test Requirements", use the interface test tool to send requests, variable settings, etc. to verify the system results. Complete this task according to the "A13-Interface Test Report Template".

2. Task requirements

(1) The interface test report should include the following contents:

① Introduction: purpose, definition of terms;

② Interface test implementation process;

③ Execution results.

(2) Tool requirements: Use PostMan related environment to complete this task.

3. Task results

XX-A13-Interface test report.doc (XX represents the station number).

Guess you like

Origin blog.csdn.net/qq_50377269/article/details/135225772
Recommended