Railway signal software testing method and system
By defining the test plan and unit test modules and conducting comprehensive testing, the problem of insufficient testing coverage in railway signal software testing is solved, the software quality and safety are improved, and the standardization and efficiency of testing work are ensured.
Patent Information
- Application Number
- CN202410923012.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-10
- Publication Date
- 2024-11-12
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
The existing technology has omissions and shortcomings in railway signal software testing, resulting in insufficient testing coverage and affecting the quality and safety of the software.
Using a railway signal software testing method and system, comprehensive testing is carried out by defining test plans and unit testing modules, including unit testing, integration testing, software confirmation testing, system integration testing and system confirmation testing, covering functional and non-functional requirements, And ensure software quality through defect tracking.
Comprehensive testing of railway signal software has been realized, software quality and safety have been improved, testing work has been carried out in a standardized and orderly manner, and testing efficiency and reliability have been improved.
Smart Images

Figure CN118939533A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of software testing, and in particular to a railway signal software testing method and system. Background Art
[0002] Railway signal software refers to the software program used for railway train signal control systems. It is mainly responsible for the functional operation and control of railway signal devices to ensure the safety and speed of train travel. In the railway transportation system, signal software plays an important role and has a very important impact on vehicle driving safety and dispatching operations.
[0003] Railway signaling software is used to manage railway transportation systems efficiently and safely to ensure the safety of personnel, equipment and the environment during train operation. In practice, the stability and reliability of railway signaling software are very important, and it is necessary to comply with relevant regulations and standards and conduct professional audits, assessments, tests and maintenance to ensure efficient operation and long-term stability of the system.
[0004] Railway signal software is directly related to the operational stability of the railway signal system. Failures can have serious consequences. The testing of railway signal software needs to be as detailed and comprehensive as possible to avoid insufficient test coverage. This also puts forward requirements for the test method to track test coverage. Summary of the invention
[0005] 1. Technical issues to be resolved
[0006] In view of the deficiencies in the prior art, the present invention provides a railway signal software testing method and system, which solves the omissions and deficiencies existing in railway signal software testing and improves the problem of software quality and security.
[0007] (II) Technical solution
[0008] To achieve the above purpose, the present invention is implemented through the following technical scheme: a railway signal software testing system, including a defined test plan and a unit test module, the defined test plan connects the design of test cases, the preparation of test data, the operation of test programs, the analysis of test results, the preparation of test reports and defect tracking processing, the unit test module includes a test unit and a software module design, the defined test plan includes a unit test module, a unit integration test module, a software confirmation test module, a system integration test module and a system confirmation test module, the unit integration test module includes an integrated unit test and a software structure design, the software confirmation test module includes a test software confirmation and a software requirement, the system integration test module includes an integrated system test and a system structure design, the system confirmation test module includes a confirmation system test and a system requirement, and the test unit, the integrated unit test, the test software confirmation, the integrated system test and the confirmation system test are connected in sequence.
[0009] Preferably, the test unit includes error reporting processing, unit modules, module interfaces, boundary conditions and judgment conditions.
[0010] Preferably, the defined test plan includes functional testing, performance testing, stress testing, capacity testing, safety testing, installation testing, security testing, recovery testing, backup testing, GUI testing and robustness testing.
[0011] Preferably, the defect tracking process includes code defects and document defects.
[0012] Preferably, the software module design, software structure design, software requirements, system structure design and system requirements are respectively connected to the test unit, integrated unit test, test software confirmation, integrated system test and confirmation system test.
[0013] Preferably, the integrated system test includes a subsystem and an interface definition file, the subsystem is bidirectionally connected to the system interface, the interface definition file is connected to present a test case, and the interface definition file is connected to the system interface.
[0014] Preferably, the test software confirmation includes an application program, the application program is connected to a support program and a database, the support program and the database are connected to an operating system, and the operating system is connected to a hardware platform.
[0015] Preferably, the definition of the test plan is connected to presenting the test plan, the presenting of the test plan is connected to designing test cases and preparing test reports, the designing of test cases is connected to presenting test cases, the presenting of test cases is connected to preparing test data, the preparing of test data is connected to presenting test data, the presenting of test data is connected to running a test program, the running of the test program is connected to presenting test results, and the presenting of test results is connected to analyzing test results.
[0016] A railway signal software testing method specifically comprises the following steps:
[0017] S1. Demand Analysis
[0018] Conduct demand research with relevant departments to clarify the functional and non-functional requirements of the software;
[0019] S2. Define the test plan
[0020] Develop overall test plans and strategies based on requirements, design test cases, cover various functional and non-functional requirements, and prepare test report templates;
[0021] S3. Unit Testing
[0022] Perform unit testing on each module of the software, verify unit functions, design unit test cases, and record and track test defects;
[0023] S4. Unit Integration Testing
[0024] Perform integration testing on interfaces and design interface test cases;
[0025] S5. Software Confirmation Test
[0026] Perform regression testing to verify defect fixes;
[0027] S6. System integration test
[0028] Conduct data migration testing and system integration testing;
[0029] S7. System confirmation test
[0030] Conduct user acceptance testing and system testing to confirm that all requirements are met;
[0031] S8. Other tests
[0032] Conduct usability and documentation testing;
[0033] S9. Test Management
[0034] Track test progress and manage test resources;
[0035] S10. Defect Management
[0036] Defect tracking, classification, and repair verification
[0037] Working principle: When testing railway signal software, first define the test plan and present the test plan, then design test cases and present the test cases, prepare test data according to the presented test cases and present the test data, run the test program according to the presented test data, present the test results, and analyze the test results according to the presented test results, prepare a test report according to the presented analyzed test results, present the test plan as the basis for designing test cases and preparing test reports, conduct defect tracking and processing, and track and handle the defects of the test.
[0038] (III) Beneficial effects
[0039] The present invention provides a railway signal software testing method and system, which has the following beneficial effects:
[0040] 1. The present invention provides a railway signal software testing method and system, which decomposes the test into different modules and levels, such as unit testing, integration testing, and system testing, and can perform comprehensive testing on the software in a more systematic manner.
[0041] 2. The present invention provides a railway signal software testing method and system. The method has corresponding testing activities in each software development stage from requirement analysis to regression testing, and can comprehensively verify the software quality. From requirement analysis to regression testing, each software development stage has corresponding testing activities, and can comprehensively verify the software quality. Test progress tracking, resource management, and defect management can ensure that the test work is carried out in a standardized and orderly manner. BRIEF DESCRIPTION OF THE DRAWINGS
[0042] Figure 1 This is a basic flow chart of software testing of the present invention;
[0043] Figure 2 It is a test schematic diagram of each test stage of the present invention;
[0044] Figure 3 This is a schematic diagram of the unit test of the present invention;
[0045] Figure 4 It is a schematic diagram of the software confirmation test composition of the present invention;
[0046] Figure 5 This is a schematic diagram of the system integration test composition of the present invention;
[0047] Figure 6 A schematic diagram of test plan composition is defined for the present invention.
[0048] Among them, 1. Define test plan; 2. Design test cases; 3. Prepare test data; 4. Run test programs; 5. Analyze test results; 6. Prepare test reports; 7. Defect tracking and processing; 8. Present test cases; 9. Present test data; 10. Present test results; 11. Present test plan; 12. Test unit; 13. Integrated unit test; 14. Test software confirmation; 15. Integrated system test; 16. Confirm system test; 17. Unit test module; 18. Unit integration test module; 19. Software confirmation test module; 20. System integration test module; 21. System confirmation test module; 22. Software module design; 23. Software structure 1. Architecture design; 24. Software requirements; 25. System architecture design; 26. System requirements; 27. Functional testing; 28. Performance testing; 29. Stress testing; 30. Capacity testing; 31. Security testing; 32. Installation testing; 33. Security testing; 34. Recovery testing; 35. Backup testing; 36. GUI testing; 37. Robustness testing; 38. Subsystem; 39. System interface; 40. Error handling; 41. Interface definition file; 42. Unit module; 43. Module interface; 44. Boundary conditions; 45. Judgment conditions; 46. Application; 47. Database; 48. Support programs; 49. Operating system; 50. Hardware platform. DETAILED DESCRIPTION
[0049] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0050] Example:
[0051] like Figure 1-6As shown, an embodiment of the present invention provides a railway signal software testing system, including defining a test plan 1 and a unit test module 17, defining the test plan 1 to connect designing test cases 2, preparing test data 3, running test programs 4, analyzing test results 5, compiling test reports 6 and defect tracking processing 7, the unit test module 17 includes a test unit 12 and a software module design 22, defining the test plan 1 includes a unit test module 17, a unit integration test module 18, a software confirmation test module 19, a system integration test module 20 and a system confirmation test module 21, the unit integration test module 18 includes an integrated unit test 13 and a software structure design 23, the software confirmation test module 19 includes a test software confirmation 14 and a software requirement 24, the system integration test module 20 includes an integrated system test 15 and a system structure design 25, the system confirmation test module 21 includes a confirmation system test 16 and a system requirement 26, and the test unit 12, the integrated unit test 13, the test software confirmation 14, the integrated system test 15 and the confirmation system test 16 are connected in sequence.
[0052] The test unit 12 includes error processing 40, unit module 42, module interface 43, boundary conditions 44 and judgment conditions 45. The test plan 1 is defined to include functional testing 27, performance testing 28, stress testing 29, capacity testing 30, security testing 31, installation testing 32, safety testing 33, recovery testing 34, backup testing 35, GUI testing 36 and robustness testing 37. The defect tracking processing 7 includes code defects and document defects.
[0053] The software module design 22, software structure design 23, software requirements 24, system structure design 25 and system requirements 26 are respectively connected to the test unit 12, the integrated unit test 13, the test software confirmation 14, the integrated system test 15 and the confirmation system test 16. The integrated system test 15 includes a subsystem 38 and an interface definition file 41. The subsystem 38 is bidirectionally connected to the system interface 39. The interface definition file 41 is connected to the presented test case 8. The interface definition file 41 is connected to the system interface 39. The test software confirmation 14 includes an application 46. The application 46 is connected to the support program 48 and the database 47. The support program 48 and the database 47 are connected to the operating system 49. The operating system 49 is connected to the hardware platform 50.
[0054] Define test plan 1 is connected to present test plan 11, present test plan 11 is connected to design test cases 2 and prepare test report 6, design test cases 2 is connected to present test cases 8, present test cases 8 is connected to prepare test data 3, prepare test data 3 is connected to present test data 9, present test data 9 is connected to run test program 4, run test program 4 is connected to present test results 10, present test results 10 is connected to analyze test results 5.
[0055] The following is a detailed description of the system architecture:
[0056] Define test plan 1: The test plan is the guidance and planning of the entire test process, including different levels of test modules and test units 12. In this system architecture, define test plan 1 connects to present test plan 11 to interact with design test cases 2 and prepare test reports 6;
[0057] Unit test module 17: Unit test module 17 is an important part of the test plan, which is used to test each unit of the software. In this system architecture, unit test module 17 includes test unit 12 and software module design 22; test unit 12 includes error processing 40, unit module 42, module interface 43, boundary condition 44 and judgment condition 45, and software module design 22 is connected with test unit 12 to ensure the integrity and accuracy of the test;
[0058] Define other modules of test plan 1: In addition to the unit test module 17, the test plan 1 also includes other modules, such as unit integration test module 18, software confirmation test module 19, system integration test module 20 and system confirmation test module 21. The purpose of these modules is to conduct comprehensive testing of the software at different stages of the testing process;
[0059] Unit integration test module 18: The unit integration test module 18 includes integrated unit test 13 and software structure design 23. The integrated unit test 13 is used to test the integration between different units, while the software structure design 23 ensures the effectiveness and correctness of the integrated test;
[0060] Software confirmation test module 19: The software confirmation test module 19 includes the test software confirmation 14 and the software requirement 24. The test software confirmation 14 is used to verify whether the software meets the requirements of the confirmation test, and the software requirement 24 is the basis for the test;
[0061] System integration test module 20: The system integration test module 20 includes integrated system test 15 and system structure design 25. The integrated system test 15 is used to test the integration of the entire system, while the system structure design 25 ensures the effectiveness and correctness of the integrated test;
[0062] System confirmation test module 21: The system confirmation test module 21 includes the confirmation system test 16 and the system requirement 26. The confirmation system test 16 is used to verify whether the system meets the requirements of the confirmation test, and the system requirement 26 is the basis for the test;
[0063] Other test plan modules: In addition to the above modules, the definition of test plan 1 also includes other test modules, such as functional testing 27, performance testing 28, stress testing 29, capacity testing 30, security testing 31, installation testing 32, safety testing 33, recovery testing 34, backup testing 35, GUI testing 36 and robustness testing 37. These test modules are used to test different aspects and functions of the software;
[0064] Defect tracking and processing 7: The defect tracking and processing 7 module includes the processing of code defects and document defects. During the testing process, if defects are found, they need to be tracked and processed in a timely manner to ensure the quality and stability of the software.
[0065] System interface 39 and interface definition file 41, in the integrated system test 15 module 20, the system interface 39 and interface definition file 41 play a key role, the system interface 39 is used for data connection:
[0066] The system mainly includes the following parts:
[0067] 1. Test case design module
[0068] This module is used to design complete and accurate test cases based on software requirements 24 and design, including:
[0069] (1) Classification: The input data is divided into legal and illegal classes, and test cases 2 are designed to cover each class.
[0070] (2) Boundary value analysis: Design test cases for the boundary values of input and output;
[0071] (3) Decision table test: Design a decision table based on program logic and generate test cases;
[0072] (4) Cause-effect diagram technology: Analyze the relationship between variables through cause-effect diagram and design test cases2;
[0073] (5) Error guessing technique: Design test cases based on possible error conditions2.
[0074] 2. Test Management Module
[0075] This module is used to plan and track test progress, resource allocation, and evaluate test results, including:
[0076] (1) Test plan: determine the test scope, test level, and test task allocation;
[0077] (2) Test tracking: Track defect repair and test progress, and generate test reports;
[0078] (3) Test evaluation: evaluate the effectiveness of test case design, test execution, and defect detection;
[0079] (4) Test resource allocation: Allocate test time, test personnel, and test environment resources.
[0080] 3. Test Automation Module
[0081] This module is used to automate test case design, test execution, and test evaluation through automation tools, mainly including:
[0082] (1) Automated testing framework: provides test case management, test execution, and result recording functions;
[0083] (2) Automated test scripts: Use programming languages to write scripts to automatically execute test cases;
[0084] (3) Test report generation: Automatically generate detailed test reports.
[0085] In summary, the railway signal software test system has achieved comprehensive and systematic testing through a perfect system architecture, improved test efficiency, and safeguarded the quality of railway signal software. Its reliable testing capabilities will further promote the advancement of railway signal technology and make railway transportation safer and more convenient.
[0086] A railway signal software testing method specifically comprises the following steps:
[0087] S1. Demand Analysis
[0088] Conduct demand research with relevant departments to clarify the functional and non-functional requirements of the software. In the demand analysis, it is necessary to clarify the key requirements of functional safety and reliability;
[0089] S2. Define the test plan
[0090] Develop an overall test plan and strategy based on requirements, design test cases, cover various functional and non-functional requirements, and prepare test report templates. In the requirements analysis, it is necessary to clarify the key requirements for functional safety and reliability;
[0091] S3. Unit Testing
[0092] Conduct unit testing on each module of the software, verify unit functions, design unit test cases, record and track test defects. In unit testing, focus on testing core functional modules, such as traffic light control and sensor detection;
[0093] S4. Unit Integration Testing
[0094] Perform integration testing on interfaces and design interface test cases. In unit testing, focus on testing core functional modules, such as traffic light control and sensor detection.
[0095] S5. Software Confirmation Test
[0096] Perform regression testing to verify defect fixes. In unit testing, focus on testing core functional modules, such as traffic light control and sensor detection.
[0097] S6. System integration test
[0098] Conduct data migration tests and system integration tests. In unit testing, focus on testing core functional modules, such as traffic light control and sensor detection.
[0099] S7. System confirmation test
[0100] Conduct user acceptance testing and system testing to confirm that all requirements are met. In unit testing, focus on testing core functional modules, such as traffic light control and sensor detection.
[0101] S8. Other tests
[0102] Usability, document testing, reliability, and security indicators require setting quantitative test goals;
[0103] S9. Test Management
[0104] Track test progress, manage test resources, and set quantitative test goals for reliability and safety indicators;
[0105] S10. Defect Management
[0106] Defect tracking, classification, and repair verification, tracking test coverage, and strengthening testing of high-risk modules.
[0107] Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the appended claims and their equivalents.
Claims
1. A railway signal software testing system, comprising a test plan definition (1) and a unit test module (17), characterized in that: The test plan definition (1) connects the design of test cases (2), the preparation of test data (3), the running of test programs (4), the analysis of test results (5), the preparation of test reports (6) and the defect tracking process (7), the unit test module (17) includes a test unit (12) and a software module design (22), the test plan definition (1) includes a unit test module (17), a unit integration test module (18), a software confirmation test module (19), a system integration test module (20) and a system confirmation test module (21), the unit integration test module (1 8) includes integrated unit testing (13) and software structure design (23), the software confirmation test module (19) includes test software confirmation (14) and software requirements (24), the system integration test module (20) includes integrated system testing (15) and system structure design (25), the system confirmation test module (21) includes confirmation system testing (16) and system requirements (26), and the test unit (12), integrated unit testing (13), test software confirmation (14), integrated system testing (15) and confirmation system testing (16) are connected in sequence.
2. A railway signal software testing system according to claim 1, characterized in that: The test unit (12) includes an error reporting process (40), a unit module (42), a module interface (43), a boundary condition (44) and a judgment condition (45).
3. A railway signal software testing system according to claim 1, characterized in that: The defined test plan (1) includes functional testing (27), performance testing (28), stress testing (29), capacity testing (30), security testing (31), installation testing (32), safety testing (33), recovery testing (34), backup testing (35), GUI testing (36) and robustness testing (37).
4. A railway signal software testing system according to claim 1, characterized in that: The defect tracking process (7) includes code defects and document defects.
5. A railway signal software testing system according to claim 1, characterized in that: The software module design (22), software structure design (23), software requirements (24), system structure design (25) and system requirements (26) are respectively connected to the test unit (12), integrated unit test (13), test software confirmation (14), integrated system test (15) and confirmation system test (16).
6. A railway signal software testing system according to claim 1, characterized in that: The integrated system test (15) includes a subsystem (38) and an interface definition file (41), wherein the subsystem (38) is bidirectionally connected to a system interface (39), and the interface definition file (41) is connected to present a test case (8), and the interface definition file (41) is connected to the system interface (39).
7. A railway signal software testing system according to claim 1, characterized in that: The test software confirmation (14) includes an application program (46), the application program (46) is connected to a support program (48) and a database (47), the support program (48) and the database (47) are connected to an operating system (49), and the operating system (49) is connected to a hardware platform (50).
8. A railway signal software testing system according to claim 1, characterized in that: The defining test plan (1) is connected to presenting the test plan (11), the presenting the test plan (11) is connected to designing test cases (2) and compiling a test report (6), the designing test cases (2) is connected to presenting test cases (8), the presenting test cases (8) is connected to preparing test data (3), the preparing test data (3) is connected to presenting test data (9), the presenting test data (9) is connected to running a test program (4), the running test program (4) is connected to presenting test results (10), and the presenting test results (10) is connected to analyzing test results (5).
9. A railway signal software testing method, characterized in that: The specific steps include: S1. Demand Analysis Conduct demand research with relevant departments to clarify the functional and non-functional requirements of the software; S2. Define the test plan Develop overall test plans and strategies based on requirements, design test cases, cover various functional and non-functional requirements, and prepare test report templates; S3. Unit Testing Perform unit testing on each module of the software, verify unit functions, design unit test cases, and record and track test defects; S4. Unit Integration Testing Perform integration testing on interfaces and design interface test cases; S5. Software Confirmation Test Perform regression testing to verify defect fixes; S6. System integration test Conduct data migration testing and system integration testing; S7. System confirmation test Conduct user acceptance testing and system testing to confirm that all requirements are met; S8. Other tests Conduct usability and documentation testing; S9. Test Management Track test progress and manage test resources; S10. Defect Management Defect tracking, classification, and fix verification.
