WO2011047625A1 - 一种系统升级后兼容性测试方法及设备 - Google Patents

一种系统升级后兼容性测试方法及设备 Download PDF

Info

Publication number
WO2011047625A1
WO2011047625A1 PCT/CN2010/077934 CN2010077934W WO2011047625A1 WO 2011047625 A1 WO2011047625 A1 WO 2011047625A1 CN 2010077934 W CN2010077934 W CN 2010077934W WO 2011047625 A1 WO2011047625 A1 WO 2011047625A1
Authority
WO
WIPO (PCT)
Prior art keywords
test
use case
playback
upgrade
result
Prior art date
Application number
PCT/CN2010/077934
Other languages
English (en)
French (fr)
Inventor
徐长久
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2011047625A1 publication Critical patent/WO2011047625A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0866—Checking the configuration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a system upgrade compatibility testing method and device. BACKGROUND OF THE INVENTION In order to ensure the compatibility of the real-time charging system (0CS, Online Charge System), it is necessary to test after the system is upgraded.
  • the existing compatibility test method is verified by a test tool or a manual dial test method, but the existing test methods are pre-constructed test scenarios and data for verification, the test efficiency is low, and the test results cannot be automatically realized before and after the system upgrade. Compare operations.
  • the inventors have found that the existing test solution has at least the following disadvantages: It is necessary to preset data first, the test efficiency is low, and automatic comparison and verification before and after the upgrade cannot be performed. Summary of the invention
  • the embodiment of the invention provides a method and a device for testing compatibility after the system is upgraded.
  • the system does not need to construct data in advance, and the system is automatically restored to the pre-test scenario for compatibility testing after the system is upgraded.
  • the embodiment of the invention provides a method for testing compatibility after system upgrade, which includes:
  • the pre-upgrade test case, the use case pre-test data, and the test result are recorded and stored;
  • the test result includes: an interactive message and a post-test data during the test;
  • System upgrade pre-upgrade test cases and use cases recorded and stored before system upgrade after system upgrade The pre-test data and the test result are subjected to the use case playback test, and the upgraded use case playback result is obtained;
  • the use case playback result includes: the use case interactive playback message during the test and the use case playback test data;
  • the system upgrade compatibility is determined according to whether the use case playback result and the recorded stored test result are consistent.
  • An embodiment of the present invention provides a compatibility testing device, including:
  • the recording and playback module is configured to record the system pre-upgrade test case, the use case test data, and the test result before the system upgrade, and obtain the use case playback result during the system upgrade use case playback test process, where the test result includes: interaction during the test Message and post-test data; the use case playback result includes: a use case playback test message during the test and a use case to play back the test data;
  • a storage module configured to store the pre-upgrade test case, the use case test data, the test result, and the use case playback result of the system
  • the test module is used to record and store the pre-upgrade test cases before the system upgrade, export the pre-test data, execute the test, and output the test results.
  • the use case playback test after the system upgrade perform the playback test to obtain the upgraded use case. Playback result;
  • the compatibility judging module is configured to judge the compatibility after the system is upgraded according to whether the use case playback result and the recorded storage test result are consistent.
  • FIG. 1 is a flowchart of a method for testing compatibility after system upgrade according to an embodiment of the present invention
  • FIG. 2 is a schematic structural diagram of a compatibility testing device according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of a method for recording a pre-upgrade OCS system according to an embodiment of the present invention
  • FIG. 4 is a flowchart of a method for testing compatibility after upgrade of an OCS system according to an embodiment of the present invention.
  • An embodiment of the present invention provides a system upgrade compatibility testing method, where the method includes the following steps:
  • Step 10 Before the system is upgraded, record and store the pre-upgrade test case, the use case test data, and the test result.
  • the test result includes: the interactive message and the post-test data during the test;
  • Step 11 Record according to the system before the upgrade and The stored system pre-upgrade test case, the use case pre-test data, and the test result are used for the use case playback test to obtain the upgraded use case playback result;
  • the use case playback result includes: the use case interactive test message and the use case playback test data; 12: Determine the compatibility of the system after the upgrade according to whether the use case playback result and the recorded stored test result are consistent.
  • the embodiment of the present invention can restore the pre-test pre-test scenario before the upgrade, and can ensure the randomness and complexity of the use case, so that the system upgrade can be fully verified by comparing the test results before and after the upgrade. Constructing data improves test automation and test efficiency.
  • Another embodiment of the present invention provides a system upgrade compatibility test method, as shown in FIG. 1, including the following steps:
  • Step 10 Before the system is upgraded, record and store the pre-upgrade test case, the use case test data, and the test result.
  • the test result includes: an interactive message and a post-test data during the test;
  • the recording device receives a recording start command sent by the user through the client, and starts the recording operation.
  • the recording operation in this embodiment can record multiple test cases for testing before the system is upgraded, and the recorded contents include: use case test data and test results (interaction messages, test data, and output words during each use case before the test is upgraded) Single, etc., you can store the recorded content in a storage module or database.
  • the recorded use cases can be displayed to the user through the client, accept the user's management, and the user's naming, classification, and selection of test cases.
  • the receiving user stops the recording by the recording stop command sent by the client.
  • the method in this embodiment is applicable to various systems that require pre-upgrade compatibility testing, such as an OCS system. If the OCS system is used, the post-test data includes an output bill.
  • Step 11 After the system is upgraded, perform the use case playback test according to the system pre-upgrade test case, the use case pre-test data and the test result recorded and stored before the system upgrade, and obtain the upgraded use case playback result;
  • the use case playback result includes: use case playback test Messages and use cases that interact during the process play back the test data;
  • the process of using the pre-upgrade test case, pre-test data, and test results recorded and stored before the system upgrade includes the following:
  • the upgraded system use case playback test is performed according to the interactive message during the test. That is, after the system is upgraded, the use case playback test is performed to test the system post-upgrade compatibility. After receiving the use case playback command input by the user through the client, the use case to be played back is selected first, and the system imports the recorded and stored use case test. Pre-test data, and load the pre-test data before the test, restore the pre-test scenario.
  • the upgraded system use case playback test according to the message exchanged during the testing process, including parsing the recorded message stream of the use case, that is, obtaining the message of the use case pre-upgrade test process interaction, for example, for the OCS system.
  • the message code stream between the real-time DCC (Dimeter Credit Control, Diameter Credit Control) and the management WebService is executed, and the playback test of the use case is performed according to the interactive message during the pre-upgrade test process to ensure the interaction during the test.
  • the message is the same as the message of the recorded pre-upgrade test process, and the result of the use case after the system upgrade is obtained.
  • the use case after the test playback data includes an output bill.
  • Step 12 Determine the system post-upgrade compatibility according to whether the use case playback result and the recorded stored test result are consistent.
  • comparing the message exchanged during the use case playback test in the use case playback result, whether the use case after the test is played back, the message exchanged during the test in the test result, and the data after the test are consistent, if they are consistent, it means compatibility, otherwise Indicates incompatibility.
  • the embodiment of the present invention can record the pre-upgrade test process, and can restore the pre-test scenario when the use case playback test is performed after the upgrade, thereby ensuring the randomness and complexity of the use case, thereby fully verifying whether the system upgrade is performed by comparing the test results before and after the upgrade. Success, the process does not require pre-constructed data to improve test automation and test efficiency.
  • the embodiment of the present invention further provides a compatibility testing device. As shown in FIG.
  • the device includes: a recording and playback module 20, configured to record a system pre-upgrade test case, a use case pre-test data, and a test result before the system is upgraded, and
  • the use case playback result is obtained during the system upgrade use case playback test process, and the test result includes: an interactive message during the test process, and the test data;
  • the use case playback result includes: the use case playback test message during the test, the use case after the test test
  • the storage module 21 is configured to store the system pre-upgrade test case, the use case pre-test data, the test result, and the use case playback result.
  • the storage module 21 can be a database.
  • the test module 22 is configured to: before the system upgrades, record and store the pre-upgrade test cases, export the use case test data, execute the test, and output the test result; perform the playback test in the use case playback test after the system upgrade, and obtain the upgrade test. Use case playback result;
  • the compatibility judging module 23 is configured to judge the compatibility of the system after the upgrade according to whether the use case playback result and the recorded storage test result are consistent.
  • the system may be an OCS system
  • the test module 22 is an OCS test module in the OCS system
  • the test data and the use case playback test data include an output bill.
  • the working principle of each module mentioned above is as follows: Before the system upgrade, after the compatibility test device receives the recording start command sent by the user, the recording and playback module 20 turns on the recording switch, and before the recording operation, the test module 22 exports the use case test. Data, the test starts to record the playback module 20 to start recording, and the test result is exported and stored in the storage module 21.
  • the test result includes: an interactive message during the test, and a test data.
  • the test module 22 imports the pre-test data of the use case from the storage module 21, loads the system, and restores the system to the test.
  • the pre-scenario, and the upgraded use case playback test is performed according to the message exchanged in the pre-upgrade test process stored in the storage module 21, and the upgraded use case playback result is obtained, and the recording module 20 exports the use case playback result to the storage module 21;
  • the judging module 23 obtains the use case playback result and the recorded stored test result from the storage module 21, and determines whether the use case playback result is consistent with the test result, thereby serving as a basis for judging the compatibility of the system after upgrade, and if consistent, compatible. Otherwise, it is incompatible, and the judgment result can be further sent to the client.
  • the compatibility test device can be connected to the client device, display the recorded and saved system pre-upgrade data to the user, accept the user's management of the pre-upgrade data of the system, and receive the use case for the user to select the playback, and can also judge the compatibility. The result is displayed by the client.
  • the compatibility test equipment can also be connected to system/analog tools such as SCP and CRM to receive analog test messages sent by the SCP, CRM, etc. system/simulation tools. It can be understood that the system and equipment for sending simulation test messages are not limited to SCP, CRM and other systems.
  • the embodiment of the present invention can record the pre-upgrade test process at any time, and can restore the pre-test scenario when testing after the upgrade, thereby ensuring the randomness and complexity of the use case, thereby fully verifying the system upgrade by comparing the test results before and after the upgrade. whether succeed.
  • This process eliminates the need to pre-configure data, increasing test automation and testing efficiency.
  • an embodiment of the present invention is applied to an OCS system as an example, in which the test module is an OCS test module, and the system is The post-upgrade compatibility test solution is described in detail.
  • the overall process is as shown in Figure 3. The following steps are included: Step 31: The user sends a start recording command to the recording and playback module of the compatibility test device through the client at any time.
  • Step 32 After the recording playback module receives the user to start the recording command, the recording switch is turned on, so that the OCS test module of the compatibility test device performs the recording operation when the test is started.
  • Step 33 An external system or a simulation tool such as SCP/CRM sends an analog test message to the OCS test module, and the simulated test message may be a charging message or a management flow message. It can be understood that after receiving the simulation test message, the OCS test module will send a corresponding response message to an external system or simulation tool such as SCP/CRM.
  • SCP/CRM an external system or simulation tool
  • Step 34 The OCS test module exports the pre-test case pre-test data to the storage module.
  • the OCS test module After receiving the analog test message, the OCS test module confirms that the recording switch has been turned on, and then exports the pre-upgrade test pre-test data, and sends the pre-upgrade use case test data to the storage module.
  • Step 35 The OCS test module starts the test, and sends a start test message to the recording and playback module. At this time, the recording and playback module starts the synchronous recording after receiving the test message, and the recording and playback module obtains the test result.
  • the OCS test module can perform system test for the environment before the pre-upgrade test, and obtain the test result.
  • the record playback module records multiple use cases of the test process.
  • Step 36 The Recording Playback module stores the recorded use cases and test results in the storage module.
  • the recording and playback module stores the use cases and test results in the storage module, and can be used for compatibility testing after the system is upgraded.
  • the test result may include: an interactive message during the test, a post-test data, etc., and the test data includes an output bill.
  • the storage module can store the pre-upgrade data in a list form, and the pre-upgrade data stored by the storage module can be displayed to the user through the client, so that the user can manage the recorded pre-upgrade data, such as classification, naming, and the like.
  • the recording playback module stops recording (not shown).
  • Step 41 The user sends a use case playback command to the compatibility test device through the client to test the compatibility of the upgraded OCS system. .
  • Step 42 After the recording playback module of the compatibility test device receives the use case playback command, the recording switch is turned on.
  • Step 43 The recording playback module notifies the storage module to load the use case playback data; that is, the notification storage module imports the use case test data that needs to be played back into the OCS test module.
  • Step 44 The OCS test module imports the pre-test data.
  • the OCS test module imports the corresponding pre-test data from the storage module and loads the data, so that the test environment of the system is restored to the pre-test environment, that is, the data is restored to the pre-test data.
  • Step 45 The OCS test module interacts with the client, and receives an analog test message sent by the user through the client.
  • the simulated message is an analog test message that is recorded during the test process recorded and stored before the OCS system is upgraded. It can be understood that the OCS test module sends a corresponding response message after receiving the client simulation test message.
  • the user can view and manage the pre-upgrade data stored in the storage module through the client, it is possible to know the interactive message during the pre-upgrade test process, and send the same message for the use case playback test when the use case is played back after the system upgrade.
  • Step 46 The OCS test module starts the use case playback test according to the simulated message, and obtains the upgraded use case playback result.
  • the use case playback result includes: a use case playback message during the test playback, and a use case to play back the test data.
  • the use case after the test playback data includes an output CDR.
  • Step 47 The Recording Playback module stores the use case playback results from the use case playback test into the storage module.
  • Step 48 The compatibility judgment module obtains the use case playback result from the storage module and the test result recorded and saved before the upgrade.
  • Step 49 The compatibility judging module compares the playback result and the test result, and sends the comparison result. To the client.
  • the content of the comparison judgment module includes: comparing the message of the interaction during the use case playback test in the use case playback result, the message of the use case after the test is played back, the message exchanged during the test in the test result, and the data after the test are consistent. If they are consistent, it means compatibility, otherwise it means incompatibility.
  • the embodiment of the present invention can record the data before the upgrade at any time, and recover the test data with high fidelity when testing after the upgrade, thereby ensuring the randomness and complexity of the use case, thereby comparing and testing before and after the upgrade.
  • the results fully verify that the system upgrade was successful. No need to pre-construct data, improve test automation, and effectively improve test efficiency.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Stored Programmes (AREA)

Description

一种系统升级后兼容性测试方法及设备 本申请要求于 2009 年 10 月 22 日提交中国专利局、 申请号为 200910236457.1 ,发明名称为"一种系统升级后兼容性测试方法及设备"的中国 专利申请的优先权， 在先申请文件的内容通过引用结合在本申请中。
技术领域 本发明涉及通信技术领域， 尤其涉及一种系统升级后兼容性测试方法及 设备。 背景技术 为保障实时计费系统（0CS， Online Charge System )升级后兼容性， 需 要在系统升级后进行测试。
现有的兼容性测试方式是通过测试工具或人工拨测方式进行验证， 但现 有的测试方法都是预先构造测试场景和数据来进行验证， 测试效率低， 且系 统升级前后测试结果无法实现自动比对操作。
在实现本发明过程中发明人发现， 该现有的测试方案至少存在如下缺点： 需要先预置数据， 测试效率低， 且无法进行升级前后的自动比对和校验。 发明内容
本发明实施例提供一种系统升级后兼容性测试方法及设备， 无需预先构 造数据， 实现系统升级后自动恢复升级前测试前场景进行兼容性测试。
本发明实施例是通过以下技术方案实现的：
本发明实施例提供一种系统升级后兼容性测试方法， 包括：
系统升级前， 录制并存储系统升级前测试用例、 用例测试前数据以及测 试结果； 所述测试结果包括： 测试过程中交互的消息和测试后数据；
系统升级后， 根据系统升级前录制并存储的系统升级前测试用例、 用例 测试前数据以及测试结果进行用例回放测试， 得到升级后用例回放结果； 所 述用例回放结果包括： 用例回放测试过程中交互的消息和用例回放测试后数 据；
根据所述用例回放结果及录制存储的测试结果是否一致来判断系统升级 后兼容性。
本发明实施例提供一种兼容性测试设备， 包括：
录制回放模块， 用于在系统升级前录制系统升级前测试用例、 用例测试 前数据以及测试结果以及在系统升级后用例回放测试过程中获得用例回放结 果， 所述测试结果包括： 测试过程中交互的消息和测试后数据； 所述用例回 放结果包括： 用例回放测试过程中交互的消息和用例回放测试后数据；
存储模块， 用于存储所述系统升级前测试用例、 用例测试前数据、 测试 结果以及用例回放结果；
测试模块， 用于在系统升级前录制并存储系统升级前测试用例时， 导出 用例测试前数据， 执行测试， 输出测试结果； 在系统升级后的用例回放测试 中， 执行回放测试， 得到升级后用例回放结果；
兼容性判断模块， 用于根据所述用例回放结果及录制存储的测试结果是 否一致来判断系统升级后兼容性。
由上述本发明实施例提供的技术方案可以看出， 本发明实施例实现了在 升级后进行测试时可任意恢复系统升级前测试前场景， 能够保证用例的随机 性和复杂性， 从而通过自动对比升级前后测试结果可充分验证系统升级是否 成功， 此过程无需预先构造数据， 提高了测试自动化程度及测试效率。 附图说明 图 1为本发明实施例一种系统升级后兼容性测试方法流程图；
图 2为本发明实施例一种兼容性测试设备结构示意图。
图 3为本发明实施例 OCS系统升级前录制方法流程图； 图 4为本发明实施例 OCS系统升级后兼容性测试方法流程图。 具体实施方式 下面将结合本发明实施例中的附图， 对本发明实施例中的技术方案进行 清楚、 完整地描述， 可以理解的是， 所描述的实施例仅仅是本发明一部分实 施例， 而不是全部的实施例。 基于本发明中的实施例， 本领域普通技术人员 在没有做出创造性劳动前提下所获得的所有其他实施例， 都属于本发明保护 的范围。
本发明实施例提供一种系统升级后兼容性测试方法， 该方法包括如下步 骤：
步骤 10: 系统升级前， 录制并存储系统升级前测试用例、 用例测试前数 据以及测试结果， 所述测试结果包括： 测试过程中交互的消息和测试后数据； 步骤 11 : 根据系统升级前录制并存储的系统升级前测试用例、 用例测试 前数据以及测试结果进行用例回放测试， 得到升级后用例回放结果； 所述用 例回放结果包括： 用例回放测试过程中交互的消息和用例回放测试后数据； 步骤 12: 根据所述用例回放结果及录制存储的测试结果是否一致来判断 系统升级后兼容性。
本发明实施例实现了在升级后进行测试时可恢复系统升级前测试前场 景， 能够保证用例的随机性和复杂性， 从而通过对比升级前后测试结果可充 分验证系统升级是否成功， 此过程无需预先构造数据， 提高了测试自动化程 度及测试效率。 本发明又一实施例提供一种系统升级后兼容性测试方法，如图 1所示， 包 括如下步骤：
步骤 10: 系统升级前， 录制并存储系统升级前测试用例、 用例测试前数 据以及测试结果， 所述测试结果包括： 测试过程中交互的消息和测试后数据； 录制设备接收用户通过客户端发送的录制开始命令， 开始录制操作。 本实施例所述录制操作可以录制系统升级前测试用多个测试用例， 录制 的内容包括： 用例测试前数据及测试结果（每个用例升级前测试过程中交互 的消息、 测试后数据、 输出的话单等） ， 可以将该录制的内容存储入存储模 块或数据库。 录制的用例可通过客户端显示给用户， 接受用户的管理， 以及 用户对测试用例的命名和分类、 选择。
录制完成后， 接收用户通过客户端发送的录制停止命令， 停止录制。 本实施例所述方法适用于各种需要进行升级前后兼容性测试的系统， 例 如 OCS系统等， 若为 OCS系统， 则所述测试后数据包括输出话单。
步骤 11 : 系统升级后， 根据系统升级前录制并存储的系统升级前测试用 例、 用例测试前数据以及测试结果进行用例回放测试， 得到升级后用例回放 结果； 所述用例回放结果包括： 用例回放测试过程中交互的消息和用例回放 测试后数据；
例如， 该根据系统升级前录制并存储的系统升级前测试用例、 用例测试 前数据以及测试结果进行用例回放测试的过程包括：
首先， 导入所述录制并存储的用例测试前数据， 根据所述测试前数据将 系统恢复为所述用例测试前场景；
之后， 按照所述测试过程中交互的消息执行升级后系统用例回放测试。 也就是系统升级后， 进行用例回放测试， 以测试系统升级后兼容性， 则 在接收到用户通过客户端输入的用例回放命令后， 先选择需要回放的用例， 系统导入录制并存储的该用例测试前数据， 并加载该用例测试前数据， 恢复 测试前场景。 之后按照所述测试过程中交互的消息执行升级后系统用例回放 测试， 包括解析录制的该用例的消息码流， 也就是获得该用例升级前测试过 程交互的消息， 例如， 对于所述 OCS系统， 包括实时 DCC ( Diameter Credit Control, Diameter信用控制）和管理 WebService之间的消息码流， 按照升级前 测试过程中交互的消息执行该用例的回放测试， 保证在测试过程中交互的消 息与所述录制的升级前测试过程交互的消息相同， 得到系统升级后用例回放 结果。 对于 OCS等计费系统， 所述用例回放测试后数据包括输出话单。
步骤 12: 根据所述用例回放结果及录制存储的所述测试结果是否一致来 判断系统升级后兼容性。
例如， 分别比对用例回放结果中的用例回放测试过程中交互的消息、 用 例回放测试后数据与测试结果中的测试过程中交互的消息、 测试后数据是否 一致， 若一致， 则表示兼容， 否则表示不兼容。
本发明实施例通过对升级前测试过程进行录制， 在升级后进行用例回放 测试时可恢复测试前场景， 能够保证用例的随机性和复杂性， 从而通过对比 升级前后测试结果可充分验证系统升级是否成功， 该过程无需预先构造数据， 提高测试自动化程度及测试效率。 本发明实施例还提供一种兼容性测试设备， 如图 2所示， 该设备包括： 录制回放模块 20， 用于在系统升级前录制系统升级前测试用例、 用例测 试前数据以及测试结果， 以及在系统升级后用例回放测试过程中获得用例回 放结果， 所述测试结果包括： 测试过程中交互的消息、 测试后数据； 该用例 回放结果包括： 用例回放测试过程中交互的消息、 用例回放测试后数据； 存储模块 21， 用于存储所述系统升级前测试用例、 用例测试前数据、 测 试结果以及用例回放结果； 该存储模块 21可以为一数据库。
测试模块 22， 用于在系统升级前录制并存储系统升级前测试用例时， 导 出用例测试前数据， 执行测试， 输出测试结果； 在系统升级后的用例回放测 试中， 执行回放测试， 得到升级后用例回放结果；
兼容性判断模块 23， 用于根据所述用例回放结果及录制存储的测试结果 是否一致来判断系统升级后兼容性。
所述系统可以为 OCS系统， 则所述测试模块 22为 OCS系统中的 OCS测试 模块， 所述测试后数据及所述用例回放测试后数据中包括输出话单。 上述各模块的工作原理一种实施例如下： 系统升级前， 当兼容性测试设 备接收到用户发送的录制开始命令后， 录制回放模块 20打开录制开关， 执行 录制操作前测试模块 22导出用例测试前数据， 测试开始同时录制回放模块 20 开始录制， 将测试结果导出保存于存储模块 21中， 所述测试结果包括： 测试 过程中交互的消息、 测试后数据。 当系统升级后， 当兼容性测试设备接收到 用户发送的用例回放命令后， 测试模块 22从所述存储模块 21中导入该用例的 所述测试前数据， 加载到该系统， 将系统恢复为测试前场景， 并按照存储模 块 21中存储的该用例升级前测试过程中交互的消息进行升级后用例回放测 试， 得到升级后用例回放结果， 录制模块 20将该用例回放结果导出到存储模 块 21 ; 兼容性判断模块 23从存储模块 21获得所述用例回放结果及录制存储的 测试结果， 判断该用例回放结果与测试结果是否一致， 从而作为判断该系统 升级后兼容性的依据， 若一致， 则兼容， 否则不兼容， 可以进一步将该判断 结果发送到客户端。
该兼容性测试设备可以与客户端设备相连， 将录制并保存的系统升级前 数据显示给用户， 接受用户对该系统升级前数据的管理， 以及接收用户选择 回放的用例， 还可以将兼容性判断结果通过所述客户端显示用户。 另外， 该 兼容性测试设备还可以与 SCP、 CRM等系统 /模拟工具相连， 以接收该 SCP、 CRM等系统 /模拟工具发送的模拟测试消息。 可以理解的是发送模拟测试消息 的系统及设备并不局限于 SCP、 CRM等系统。
本发明实施例通过对升级前测试过程在任意时刻进行录制， 在升级后进 行测试时可以恢复测试前场景， 能够保证用例的随机性和复杂性， 从而通过 对比升级前后测试结果可充分验证系统升级是否成功。 此过程无需预先构造 数据， 提高测试自动化程度以及测试效率。 为进一步理解本发明上面实施例的技术方案， 下面结合附图以本发明实 施例应用于 OCS系统为例，在该 OCS系统中测试模块为 OCS测试模块，对系统 升级后兼容性测试方案进行详细说明， 总体流程如图 3所示， 包括如下步骤： 步骤 31 : 用户在任意时刻通过客户端向兼容性测试设备的录制回放模块 发送开始录制命令。
步骤 32: 录制回放模块接收用户开始录制命令后， 打开录制开关， 这样 兼容性测试设备的 OCS测试模块在开始执行测试时就执行录制操作。
步骤 33 : SCP/CRM等外部系统或模拟工具， 向 OCS测试模块发送模拟 测试消息， 该模拟测试消息可以为计费消息或管理流程消息等。 可以理解的 是 OCS测试模块收到该模拟测试消息后会发送相应的响应消息给 SCP/CRM等 外部系统或模拟工具。
步骤 34: OCS测试模块导出升级前用例测试前数据给存储模块。
OCS测试模块在接收到模拟测试消息后， 确认录制开关已经打开， 则导 出升级前用例测试前数据， 并将升级前用例测试前数据发送给存储模块。
步骤 35: OCS测试模块开始测试， 并向录制回放模块发送开始测试消息， 此时录制回放模块接收该测试消息后开始同步录制， 并且录制回放模块获得 测试结果。
OCS测试模块可以以该升级前测试前数据为环境进行系统测试， 得到测 试结果， 录制回放模块对测试过程的多个用例进行录制。
步骤 36: 录制回放模块将录制的用例和测试结果存入存储模块。
录制回放模块将用例以及测试结果存储入存储模块， 可以待后续系统升 级后进行兼容性测试使用。 该测试结果可以包括： 测试过程中交互的消息、 测试后数据等， 该测试后数据包括输出话单。 存储模块可以以列表形式存储 该升级前数据， 该存储模块存储的升级前数据可以通过客户端显示给用户， 以便用户对该录制的升级前数据进行管理， 例如分类、 命名等。
在录制完成后， 接收到用户通过客户端发送的停止录制命令， 则录制回 放模块停止录制 （图中未示出） 。
上述操作完成了对升级前 OCS系统测试过程的录制，在 OCS系统升级后， 为测试升级后系统的兼容性， 如图 4所示， 本发明实施例提供如下操作方法： 步骤 41 : 用户通过客户端向兼容性测试设备发送用例回放命令， 以测试 升级后 OCS系统的兼容性。
步骤 42: 兼容性测试设备的录制回放模块接收到用例回放命令后， 打开 录制开关。
步骤 43: 录制回放模块通知存储模块加载用例回放数据； 即通知存储模 块将需要回放的用例测试前数据导入到 OCS测试模块。
步骤 44: OCS测试模块导入用例测试前数据。
OCS测试模块从存储模块中导入相应的用例测试前数据，并加载该数据， 使系统的测试环境恢复为测试前环境， 即恢复为计费测试前数据。
步骤 45: OCS测试模块与客户端交互， 接收用户通过客户端发送的模拟 测试消息， 该模拟消息为 OCS系统升级前录制并存储的测试过程中交互的模 拟测试消息。 可以理解的是， 该 OCS测试模块在接收到客户端模拟测试消息 后会发送相应的响应消息。
由于用户可通过客户端查看、 管理存储模块存储的系统升级前数据， 因 此可以知道升级前测试过程中交互的消息， 并在系统升级后进行用例回放时， 发送同样的消息进行用例回放测试。
步骤 46: OCS测试模块按照所述模拟消息开始用例回放测试， 得到升级 后用例回放结果。
所述用例回放结果包括： 用例回放测试过程中交互的消息、 用例回放测 试后数据， 该用例回放测试后数据包括输出话单。
步骤 47: 录制回放模块将用例回放测试得到的用例回放结果存入存储模 块。
步骤 48: 兼容性判断模块从存储模块中获取该用例回放结果以及升级前 录制并保存的测试结果。
步骤 49: 兼容性判断模块比对回放结果及测试结果， 将该比对结果发送 到客户端。
兼容性判断模块进行比对的内容包括： 分别比对用例回放结果中的用例 回放测试过程中交互的消息、 用例回放测试后数据与测试结果中的测试过程 中交互的消息、 测试后数据是否一致， 若一致， 则表示兼容， 否则表示不兼 容。
综上所述， 本发明实施例通过对升级前场景在任意时刻进行录制， 在升 级后进行测试时可高保真地恢复测试数据， 能够保证用例的随机性和复杂性， 从而通过对比升级前后测试结果可充分验证系统升级是否成功。 无需预先构 造数据， 提高测试自动化程度， 有效提高了测试效率。
本领域普通技术人员可以理解， 实现上述实施例方法中的全部或部分步 骤是可以通过程序来指令相关的硬件完成， 所述的程序可以存储于一计算机 可读存储介质中，例如只读存储器（简称 ROM )、随机存取存储器（简称 RAM )、 磁盘、 光盘等。
以上所述， 仅为本发明较佳的具体实施方式， 但本发明的保护范围并不 局限于此， 任何熟悉本技术领域的技术人员在本发明揭露的技术范围内， 可 轻易想到的变化或替换， 都应涵盖在本发明的保护范围之内。 因此， 本发明 的保护范围应该以权利要求的保护范围为准。

Claims

权利要求 书
1、 一种系统升级后兼容性测试方法， 其特征在于， 包括：
系统升级前， 录制并存储系统升级前测试用例、 用例测试前数据以及测试 结果； 所述测试结果包括： 测试过程中交互的消息和测试后数据；
系统升级后， 根据系统升级前录制并存储的系统升级前测试用例、 用例测 试前数据以及测试结果进行用例回放测试， 得到升级后用例回放结果； 所述用 例回放结果包括： 用例回放测试过程中交互的消息和用例回放测试后数据； 根据所述用例回放结果及录制存储的测试结果是否一致来判断系统升级后 兼容性。
2、 如权利要求 1所述的方法， 其特征在于， 所述根据所述录制并存储的系 统升级前测试用例、 用例测试前数据以及测试结果进行用例回放测试包括： 导入所述录制并存储的用例测试前数据， 根据所述测试前数据将系统恢复 为所述用例测试前场景；
按照所述测试过程中交互的消息执行升级后系统用例回放测试。
3、 如权利要求 2所述的方法， 其特征在于， 导入所述录制并存储的用例测 试前数据前还包括：
接收用例回放命令， 从存储的所述系统升级前测试用例中选择需要回放的 用例。
4、 如权利要求 1所述的方法， 其特征在于， 所述根据所述用例回放结果及 录制存储的测试结果是否一致来判断系统升级后兼容性包括：
若所述用例回放结果及存储的测试结果一致， 则表示兼容， 否则表示不兼 容。
5、 如权利要求 1至 4中任一项所述的方法， 其特征在于， 所述系统为实时计 费系统 OCS， 则所述测试后数据及所述用例回放测试后数据中包括输出话单。
6、 一种兼容性测试设备， 其特征在于， 包括：
录制回放模块， 用于在系统升级前录制系统升级前测试用例、 用例测试前 数据以及测试结果以及在系统升级后用例回放测试过程中获得用例回放结果， 所述测试结果包括： 测试过程中交互的消息和测试后数据； 所述用例回放结果 包括： 用例回放测试过程中交互的消息和用例回放测试后数据；
存储模块， 用于存储所述系统升级前测试用例、 用例测试前数据、 测试结 果以及用例回放结果；
测试模块， 用于在系统升级前录制并存储系统升级前测试用例时， 导出用 例测试前数据， 执行测试， 输出测试结果； 在系统升级后的用例回放测试中， 执行回放测试， 得到升级后用例回放结果；
兼容性判断模块， 用于根据所述用例回放结果及录制存储的测试结果是否 一致来判断系统升级后兼容性。
7、 如权利要求 6所述的设备， 其特征在于， 所述系统为实时计费系统 OCS， 则所述测试后数据及所述用例回放测试后数据中包括输出话单。
8、 如权利要求 7所述的设备， 其特征在于， 所述测试模块为 OCS测试模块。
PCT/CN2010/077934 2009-10-22 2010-10-21 一种系统升级后兼容性测试方法及设备 WO2011047625A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910236457.1 2009-10-22
CN 200910236457 CN102045191B (zh) 2009-10-22 2009-10-22 一种系统升级后兼容性测试方法及设备

Publications (1)

Publication Number Publication Date
WO2011047625A1 true WO2011047625A1 (zh) 2011-04-28

Family

ID=43899838

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/077934 WO2011047625A1 (zh) 2009-10-22 2010-10-21 一种系统升级后兼容性测试方法及设备

Country Status (2)

Country Link
CN (1) CN102045191B (zh)
WO (1) WO2011047625A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107222368A (zh) * 2017-06-29 2017-09-29 北京奇艺世纪科技有限公司 一种数据重放方法及装置

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103631705B (zh) * 2012-08-24 2018-01-05 百度在线网络技术（北京）有限公司 一种针对搜索引擎的回归测试方法和装置
DE102012023412A1 (de) * 2012-11-30 2014-06-05 Dräger Medical GmbH Pumpenkompatibilitätstest
CN105279063B (zh) * 2014-07-25 2019-11-22 腾讯科技（深圳）有限公司 一种测试方法、装置及服务器
CN104615787B (zh) * 2015-03-06 2018-05-18 中国建设银行股份有限公司 一种更新界面显示方法及装置
CN106897204A (zh) * 2015-12-17 2017-06-27 中国电信股份有限公司 业务流程的自动监测方法和系统
CN106941420B (zh) * 2017-03-16 2019-12-13 北京深思数盾科技股份有限公司 一种集群应用环境升级方法及装置
CN107707433B (zh) * 2017-11-14 2020-12-11 北京思特奇信息技术股份有限公司 一种从网络平台测试业务流程的方法及计算机设备
CN107872352B (zh) * 2017-11-27 2021-08-24 瑞斯康达科技发展股份有限公司 一种网管系统的性能测试方法、装置及系统
CN109918293B (zh) * 2019-01-29 2024-05-03 平安科技（深圳）有限公司 系统测试方法及装置、电子设备、计算机可读存储介质
CN110221958B (zh) * 2019-04-15 2023-06-06 创新先进技术有限公司 应用测试方法、装置、计算设备及计算机可读存储介质
CN110362479B (zh) * 2019-06-19 2023-07-14 平安科技（深圳）有限公司 系统升级测试方法和系统
CN111782250A (zh) * 2020-08-11 2020-10-16 杭州溪塔科技有限公司 一种软件升级兼容性测试方法、系统及存储介质
CN113835727A (zh) * 2021-08-31 2021-12-24 贝壳技术有限公司 配置版本升级方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040015868A1 (en) * 2001-05-10 2004-01-22 International Business Machnies Corporation Beta version processing system
CN1791258A (zh) * 2005-12-29 2006-06-21 北京握奇数据系统有限公司 智能卡的测试方法
CN101242621A (zh) * 2008-01-21 2008-08-13 中兴通讯股份有限公司 一种基于界面的自动化测试方法及系统
CN101382914A (zh) * 2008-10-15 2009-03-11 北大方正集团有限公司 软件更新文件的测试方法和装置
CN101727383A (zh) * 2008-10-16 2010-06-09 上海市医疗保险信息中心 数据库的仿真测试方法和系统

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100334917C (zh) * 2004-12-31 2007-08-29 大唐微电子技术有限公司 一种用户识别模块工具套件卡的兼容性测试方法及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040015868A1 (en) * 2001-05-10 2004-01-22 International Business Machnies Corporation Beta version processing system
CN1791258A (zh) * 2005-12-29 2006-06-21 北京握奇数据系统有限公司 智能卡的测试方法
CN101242621A (zh) * 2008-01-21 2008-08-13 中兴通讯股份有限公司 一种基于界面的自动化测试方法及系统
CN101382914A (zh) * 2008-10-15 2009-03-11 北大方正集团有限公司 软件更新文件的测试方法和装置
CN101727383A (zh) * 2008-10-16 2010-06-09 上海市医疗保险信息中心 数据库的仿真测试方法和系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107222368A (zh) * 2017-06-29 2017-09-29 北京奇艺世纪科技有限公司 一种数据重放方法及装置
CN107222368B (zh) * 2017-06-29 2020-04-17 北京奇艺世纪科技有限公司 一种数据重放方法及装置

Also Published As

Publication number Publication date
CN102045191B (zh) 2013-03-20
CN102045191A (zh) 2011-05-04

Similar Documents

Publication Publication Date Title
WO2011047625A1 (zh) 一种系统升级后兼容性测试方法及设备
TWI743405B (zh) 語音播報方法、智慧型播報裝置、編碼有電腦程式指令的一個或多個非暫時性電腦儲存媒體以及智慧型播報設備
CN102880532B (zh) 以云端技术为基础的测试系统与方法
CN109117235B (zh) 一种业务数据处理方法、装置以及相关设备
CN109788033B (zh) 无人车远程调试方法、装置、系统及存储介质
CN109951547A (zh) 事务请求并行处理方法、装置、设备和介质
CN113077302B (zh) 换电柜的处理方法、系统、设备以及存储介质
CN103731413A (zh) 一种处理异常登录的方法
CN114374632B (zh) 一种物联网数据平台多协议测试提效方法
CN108288168A (zh) 借贷服务账户的注册方法、终端和计算机可读存储介质
CN110768863A (zh) 一种模拟测试aiot设备的方案
CN107182042A (zh) 短信通道质量评估方法、装置、介质和系统
CN106210032A (zh) 基于终端数据批量上报的方法及装置
CN107861836A (zh) 行车记录仪数据备份方法和装置
CN106850518A (zh) 安全认证方法及装置
CN110138767A (zh) 事务请求的处理方法、装置、设备和存储介质
CN111080420A (zh) 一种实现多供应商话费充值匹配的方法、系统及存储介质
CN107678851A (zh) 一种开启应用程序的方法和第一终端
CN113111125B (zh) 一种基于区块链的业务存证方法
CN104796867A (zh) 一种主动登录的方法及终端
CN112463557A (zh) 一种用户空间操作的记录方法、装置和介质
CN108650265A (zh) 文件的下载方法及其装置、存储介质、电子终端
WO2017167068A1 (zh) 电话号码的变更校验方法、装置和系统
CN112527468A (zh) 一种联盟链一站式自动部署与测试方法及系统
CN106375109A (zh) 一种交换机配置模拟下发的方法、系统及计算机

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10824466

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10824466

Country of ref document: EP

Kind code of ref document: A1