会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 51. 发明申请
    • SYSTEM, METHOD, AND COMPUTER PROGRAM PRODUCT FOR ERROR CODE INJECTION
    • 用于错误代码注入的系统,方法和计算机程序产品
    • US20140289567A1
    • 2014-09-25
    • US14295644
    • 2014-06-04
    • International Business Machines Corporation
    • Gerard M. DearingTerri A. Menendez
    • G06F11/36
    • G06F11/3684G06F11/3604G06F11/3624G06F11/3632G06F11/3664G06F11/3672G06F11/3676G06F11/3696
    • In various embodiments, a method, system, and computer program product for injecting error code include logic and/or program instructions configured for determining critical points in executing code of software under test, building a testcase to invoke the software under test, determining an appropriate response action for each critical point based on an error encountered at each critical point, injecting a critical point segment into the executing code at a corresponding critical point, and outputting a unique identifier of each critical point segment, the testcase being configured to issue commands, with each command limiting which of one or more critical points remains active based on one of: a number of times the one or more critical points have been accessed in the executing code, a number of times a critical point has been skipped, and an amount of times a critical point has been accessed versus skipped.
    • 在各种实施例中,用于注入错误代码的方法,系统和计算机程序产品包括被配置用于确定在执行被测软件的代码中的关键点的逻辑和/或程序指令,构建测试用例以调用被测软件, 基于在每个关键点处遇到的错误对每个关键点的响应动作,将关键点段注入到相应关键点处的执行代码,以及输出每个关键点段的唯一标识符,所述测试用例被配置为发出命令, 每个命令限制一个或多个关键点中的哪个关键点保持活动,基于以下之一:在执行代码中访问了一个或多个关键点的次数,临时点被跳过的次数,以及数量 的时间已经被访问了一个关键点,而不是跳过。
    • 54. 发明授权
    • Streamlining unit testing through hot code swapping
    • 通过热代码交换来简化单元测试
    • US08799875B2
    • 2014-08-05
    • US12894900
    • 2010-09-30
    • Leo ZieglerVincent J. Hardy
    • Leo ZieglerVincent J. Hardy
    • G06F9/44
    • G06F11/3696
    • Methods and systems are described for testing methods and other functions by swapping external functions for mock functions. A test case definition is entered by a programmer, which can specify the expected number of arguments and argument values of external function or method calls, the context state, the return value, and any expected error conditions. The test case definition is used by a function tester to automatically create mock functions, modify the target function so that it calls the mock functions, execute the target function with specified arguments and a test context, and then compare the results to expected results.
    • 通过交换模拟功能的外部功能,描述了测试方法和其他功能的方法和系统。 程序员输入测试用例定义,可以指定外部函数或方法调用的预期参数数量,参数值,上下文状态,返回值以及任何预期的错误条件。 测试用例定义由函数测试者自动创建模拟函数,修改目标函数,调用模拟函数,使用指定参数和测试上下文执行目标函数,然后将结果与预期结果进行比较。
    • 56. 发明申请
    • AUTOMATED END-TO-END TESTING VIA MULTIPLE TEST TOOLS
    • 通过多种测试工具自动进行端到端测试
    • US20140181590A1
    • 2014-06-26
    • US13721480
    • 2012-12-20
    • Marcus Wefers
    • Marcus Wefers
    • G06F11/36
    • G06F11/3688G06F11/3696
    • The development of automated tests that span end-to-end business processes, such as may be executed in part by each of multiple Enterprise Resource Planning systems, is a very complex activity. Beside expert know-how of various tools, such end-to-end business process testing requires various test automation tools to cover complex business processes to provide automated tests. Various embodiments herein are built on an approach for building and connecting automated end-to-end tests that combines test scripts from multiple test tools. These embodiments include functionality to assemble test scripts from multiple test tools into a single, composite test script that allows passing of information between the test scripts during performance of an end-to-end automated process test. These and other embodiments are illustrated and described herein.
    • 跨越端到端业务流程的自动化测试的开发,例如可能由多个企业资源规划系统中的每一个部分执行,这是非常复杂的活动。 除了各种工具的专业知识外,这种端到端业务流程测试需要各种测试自动化工具来覆盖复杂的业务流程以提供自动化测试。 本文中的各种实施方式建立在一种构建和连接自动化端到端测试的方法,该测试结合了来自多个测试工具的测试脚本。 这些实施例包括将测试脚本从多个测试工具组装成单个复合测试脚本的功能,该脚本允许在执行端到端自动化过程测试期间在测试脚本之间传递信息。 这些和其他实施例在本文中示出和描述。
    • 57. 发明授权
    • Method and system for automatic identification of missing test scenarios
    • 自动识别缺失测试场景的方法和系统
    • US08739128B1
    • 2014-05-27
    • US13103078
    • 2011-05-08
    • Yossi CohenMati CohenNurit DorDror Weiss
    • Yossi CohenMati CohenNurit DorDror Weiss
    • G06F9/45
    • G06F11/36G06F8/30G06F9/44589G06F11/263G06F11/3604G06F11/3672G06F11/368G06F11/3696
    • Identifying missing test scenarios based on a repository of organization-specific in-use scenarios, including: accessing a set of organization-specific in-use scenarios, each organization-specific in-use scenario executes least two transactions; comparing the organization-specific in-use scenarios with available test scenarios repairable by a non-programmer user, each available test scenario repairable by a non-programmer user tests at least two transactions; identifying organization-specific in-use scenarios that do not have corresponding test scenarios repairable by a non-programmer user; and providing at least one of the missing test scenarios to a non-programmer user for generating a test scenario repairable by a non-programmer user that covers the at least one missing test scenario.
    • 根据特定于组织的使用场景的存储库识别缺失的测试场景,包括:访问一组特定于组织的在用场景,每个组织特定的在用场景都执行最少两个事务; 将组织特定的在用场景与可由非程序员用户修复的可用测试场景进行比较,每个可用的测试场景由非程序员用户可修复至少测试两个事务; 识别不具有可由非程序员用户修复的相应测试场景的特定于组织的使用场景; 以及向所述非程序员用户提供至少一个所述缺失的测试场景,用于生成可由非程序员用户修复的覆盖所述至少一个缺失测试场景的测试场景。
    • 59. 发明申请
    • RESILIENT MOCK OBJECT CREATION FOR UNIT TESTING
    • 用于单元测试的灵活的MOCK对象创建
    • US20140095142A1
    • 2014-04-03
    • US13633291
    • 2012-10-02
    • INTERNATIONAL BUSINESS MACHINES CORPORATION
    • Timothy J. Baldwin
    • G06F9/45
    • G06F11/3696
    • Embodiments of the invention provide a method, system and computer program product for fault alerting in mock object supported unit testing. In an embodiment of the invention, a method for fault alerting in mock object supported unit testing is provided. The method includes creating in memory of a computing system an instance a mock object proxying for an object under test by test code and proxying by method name an invocation of a method in the object under test to the mock object. The method also includes determining whether or not a method exists in memory for the mock object corresponding to the method name. Finally, the method includes invoking an exception handler for the mock object outputting error text indicating a non-presence of a method associated with the method name responsive to a method by the method name not existing in the memory for the mock object, but otherwise invoking a method that exists in the memory of the mock object corresponding to the method name.
    • 本发明的实施例提供了用于模拟对象支持的单元测试中的故障报警的方法,系统和计算机程序产品。 在本发明的实施例中,提供了一种用于模拟对象支持的单元测试中的故障报警的方法。 该方法包括在计算系统的存储器中创建一个实例,通过测试代码代理被测对象的模拟对象,并通过方法名称代理被测对象中的方法到模拟对象。 该方法还包括确定对应于方法名称的模拟对象的存储器中是否存在方法。 最后,该方法包括调用模拟对象的异常处理程序,该异常处理程序通过方法名不存在于模拟对象的存储器中的方法名称来输出指示不存在与方法名称相关联的方法的错误文本,但是以其他方式调用 存在于与该方法名称相对应的模拟对象的存储器中的方法。