1189 results about "Testing software" patented technology

Embodiments relate to systems and methods for testing and evaluating software in the network cloud. A developer or other operator may wish to debug, modify, or update a set of test software based on testing of that software. The developer can instantiate a set of virtual servers or other test beds in the cloud, and install the subject software to the virtual test beds. A test management module can monitor the execution of the set of test software on the set of virtual test beds, to detect execution faults, measure processing performance, stress-test the software with predetermined data inputs, and manage other aspects of software life cycle development. The test management module can provide or access a set of application programming interfaces to a set of software tools external to the cloud, so that the set of test software can be tested and optimized using external programming development tools.

Systems and methods are described for testing a software module. The method comprises receiving a modified software module for use as part of a software application which includes a plurality of constituent software modules, replacing at least one of the constituent software modules with the modified software module to generate a modified software application, generating output data as a function of execution of the modified software application, and storing the output data.

Disclosed is a device and method for testing of a program or a design of an electronic device comprising digital logic circuitry. The method comprises testing the design of software or an electronic device and injecting, after initiation of the testing step, a predetermined error pattern into a value operated upon by the design of the digital logic circuitry. In a preferred embodiment, the software is a simulation of the design of a processor having a cache with error detection and / or correction circuitry. A triggering condition is preferably a cache hit, in response to which a detectable error is injected into the cache. The simulated operations of the model are observed to determine whether the injected error is detected, as should happen if the processor's error detection circuitry has been designed properly. In another respect, the invention is an apparatus, or computer software embedded on a computer readable medium, for testing a program comprising an error detector. The apparatus or software comprises the program, an error injector module connected to the program; and a checker module connected to the program. The checker module is capable of determining whether the program responds appropriately to an error dynamically produced by the error injector module during execution of the program. By injecting errors dynamically the invention easily facilitates precisely focused testing at any time during simulated operation regardless of initialization conditions.

A method for automatically maintaining a database that stores coverage data for testing software code under development is provided. The method includes providing modified instrumented software and using test cases of a test suite to execute the modified instrumented software. Modified coverage data that includes a call tree defining a path of each test case is created. The method also includes replacing the coverage data with the modified coverage data at scheduled intervals.

A system and method for improved testing of a software build is provided. The system and method automatically track differences between software builds by scanning the binaries of a software product to automatically discover its classes. The system and method then build a detailed dictionary that captures static and dynamic information of that build, including class dependencies. A comparison may be made with another build, so that the present invention may automatically execute selective tests on any types, and their dependencies, that have had a structural or behavioral modification since the last build. Testers may load a set of constructors for any specific types to further increase coverage of types (or classes) tested. The present invention may also provide detailed reports that may be used to drive future testing work and target specific areas of the code for additional testing. The system and method may further provide code generation from intermediate code to specified targets to aid in reproducing and fixing bugs.

A test result analyzer for processing results of testing software. The analyzer has an interface emulating the interface of a traditional data logger. After analyzing the test results, selected results may be output to a log file or otherwise reported for subsequent use. The test result analyzer compares test results to results in a database of historical data from running test cases. The analyzer filters out results representative of fault conditions already reflected in the historical data, thereby reducing the amount of data that must be processed to identify fault conditions.

The invention discloses a method and a system for realizing automatic software testing. The method includes the following steps: obtaining the object code of the to-be-tested software; obtaining the test case for the to-be-tested software, wherein the test case is generated by adopting the oriented object technology and includes a test object key word and a test drive data for the to-be-tested software; compiling and saving the test script according to the test case; running the test script, so as to carry out the automatic software testing of the object code of the to-be-tested software based on the test object key word and the test drive data. By adopting the solution of automatic testing and utilizing the object oriented test case to carry out the automatic testing based on the assemblage of the test object key word and the test drive data, the automatic software testing can be realized without the participation of any operator, and the method and the system for realizing automatic software testing are applicable to all the stages of software testing.

The integrated test framework of the present invention includes a test framework runtime that executes test scripts and that also allows a script to identify a variation tool called a “data provider” that is responsible for providing data to the test framework runtime and controlling the iteration of the runtime through the variations. The script also identifies the type of data set from which the data provider should obtain the data from which the variations are derived and the location of the data set. Multiple variation data providers may be used in conjunction with an adapter layer that coordinates the iteration of each variation data provider and creates an aggregated variation over multiple varying parameters of different scope.

The integrated test framework of the present invention includes a test framework runtime that executes test scripts and that also allows a script to identify a variation tool called a “data provider” that is responsible for providing data to the test framework runtime and controlling the iteration of the runtime through the variations. The script also identifies the type of data set from which the data provider should obtain the data from which the variations are derived and the location of the data set. Multiple variation data providers may be used in conjunction with an adapter layer that coordinates the iteration of each variation data provider and creates an aggregated variation over multiple varying parameters of different scope.

Systems and methods of testing, of software applications, based on business process models are described herein. In one example, the method comprises receiving, by a processor, the at least one business process model, wherein the at least one business process model is indicative of a business process associated with the software application and analyzing, by the processor, the at least one business process model to identify at least one test scenario. The method further comprises generating, by the processor, a set of test cases and test data for the at least one test scenario and producing, by the processor, a set of test automation scripts based on one or more keywords associated with the at least one test scenario.

A system for and method of modeling thermal performance characteristics of HVAC components in a building uses the building power or other meter to measure power consumed by the components. The models are used to test the components, preferably during off hours, to ensure proper and efficient operation. Preferably, the testing software is written in a high-level interpretive language that is independent of the HVAC component being modeled. The models are adaptively maintained by periodically ensuring that their measured output matches the predicted output. When the two do not match, the model parameters are updated. These models can also be used to generate reports comparing costs and cost savings for different temperature and other environmental settings within selected zones in the building.

A method and process for developing and testing software applies runtime executable patching technology to enhance the quality assurance effort across all phases of the Software Development Life-Cycle in a "grey box" methodology. The system facilitates the creation of re-usable, Plug"n'Play Test Components, called Probe Libraries, that can be used again and again by testers as well as developers in unit and functional tests to add an extra safety net against the migration of low-level defects across Phases of the overall Software Development and Testing Life-Cycle. The new elements introduced in the Software Development Life-Cycle focus on bringing developers and testers together in the general quality assurance workflow and provide numerous tools, techniques and methods for making the technology both relatively easy to use and powerful for various test purposes.

A digital system provides a serial bus diagnostic port such as, for example, a universal serial bus (USB) diagnostic port. The USB diagnostic port can include a USB slave device operable to interface to a universal serial bus, a flash memory controller interface coupled to the USB slave device and operable to interface to a flash memory controller, and a test access port controller coupled to the USB slave device and operable to interface to a test access port. The diagnostic port can further include a system interface coupled to the USB slave device and operable to interface to an integrated controller independently of an operating system. Via the diagnostic port, a USB testing tool with testing software can access and debug internal logic of the digital system. As an alternative to a USB diagnostic port, the serial bus diagnostic port can be implemented in a variety of wired or wireless implementations such as, for example, an I.E.E.E. 1394 diagnostic port, an Ethernet diagnostic port, or a wireless Internet diagnostic port. Further, the serial bus diagnostic port can, for example, be used for software development, in-factory testing or in-field diagnostics of the digital system.

A method and device with instructions for testing a software application include creating a system model for the software application, wherein the system model includes an activity diagram, and applying one or more test annotations to the activity diagram to control test generation for testing the software application. Further, test annotations and the system model are processed to create one or more test cases, and the software application is tested using a test execution tool that uses the test cases.

A system and method for generating and / or managing virtual network(s) is provided. The system provides an interface for end-user(s) to create a virtual network (e.g., on-demand). The virtual network comprises a plurality of servers that allow the user to, for example, develop and / or test software, migrate applications, apply tasks and / or troubleshoot scenarios in a simulated, distributed environment. A user can communicate with the system via an interface (e.g., web-based) to create and / or manage the virtual network. Additionally, the system can employ a common infrastructure to facilitate creation and / or management of a variety of virtual deployment configurations. The common infrastructure can be designed, for example, by administrator(s) having knowledge of hardware and / or software available for employment within the virtual network. The system can further provide a load-balancing mechanism to determine and / or distribute workload to computer(s) with available resource(s). Additionally, the system can expire virtual session(s) that are no longer in use thereby releasing resources for other user(s) and / or session(s).

A functional testing and evaluation technique is provided employing an abstraction matrix that describes a complex software component to be tested. The abstraction matrix includes at least one test case scenario and mapped expected results therefore. Test cases are derived from the at least one test case scenario and used to test the software component, thereby generating test results. The test results are automatically evaluated using the abstraction matrix. The evaluating includes comparing a test case to the at least one test case scenario of the abstraction matrix and if a match is found, comparing the test result for that test case with the mapped expected result therefore in the abstraction matrix.

A method, apparatus, and computer instructions for testing software programs running on a data processing system. Text is translated from the source language to the target language to form translated text in response to a user input, containing the text in a source language. The text is entered through a computer interface in the data processing system. The translated text is inserted into a user interface of the software program to be tested to form inserted, translated text. The software program is written using the target language. A determination is made as to whether the software program functions correctly using the inserted, translated text.

Some embodiments of the present invention provide a system that tests a software program. During operation, the system traces a flow of tainted data through the software program during execution of the software program. Next, the system alters the flow by modifying an instruction within the software program. The system then monitors the behavior of the software program after modifying the instruction. Finally, the system analyzes a correctness of the software program based on the monitored behavior.

A computer-implemented system and method for improving the efficiency of testing a process by focusing the testing in the highest risk areas of the process. One application of this computer-implemented system and method is in software testing to improve the effectiveness of software testing by focusing the testing efforts on the parts of the software that have a highest risk of failure and also by focusing the testing on the types of tests needed to reduce the risk.

The invention relates to a device and a method for testing the LED light source intensity space distribution characteristic. The device comprises a base, a testing sample seat, a light intensity detecting unit, a detector bracket, a testing circuit, a computer and testing software. A multi-path synchronous testing method of a plurality of light intensity detecting units is adopted to replace one light intensity detector to sequentially test a plurality of points so as to realize the quick testing of the LED light source intensity space distribution characteristic. Compared with a conventional light distribution curve measuring method adopting one light intensity detector, if N light intensity detectors are used, the testing speed can be improved by more than N times. The device has the advantages of high testing speed and precision, abundant information content and real time and visualization.

The invention includes a method for determining a software reliability metric, including obtaining testing defect data, obtaining test case data, determining testing exposure time data using the test case data, and computing the software reliability metric using testing defect data and testing exposure time data. The defect data includes software defect records. The test case data includes test case execution time data. A testing results profile is determined using testing defect data and testing exposure time data. A software reliability model is selected according to the testing results profile. A testing defect rate and a number of residual defects are determined by using the software reliability model and the testing results profile. A testing software failure rate is determined using the testing defect rate and the number of residual defects. A field software availability metric is determined using the field software failure rate determined using the testing software failure rate.

A method and system for testing a software application. A description of a test suite for testing the software application being tested (ABT) is inserted into a test database. The ABT is invokes multiple external software applications during execution of a test script of the test suite. Each external application invoked by the ABT is replaced by a corresponding simulator during execution of the test script. Output data to be returned to the ABT by each invoked simulator is inserted into the test database, after which each test script of the test suite is executed. The executing includes: sending a request, by the ABT to each simulator invoked in each test script, for requested data; and receiving, by the ABT, the requested data from each simulator invoked in each test script. The received requested data includes the output data that had been inserted into the test database.

The present invention provides a method, apparatus, and computer instructions for testing compatibility of software versions, the method comprising the computer implemented steps of performing an inventory on an existing set of software modules resident in the data processing system responsive to an installation of a new software module in a data processing system; referring to a knowledge base of versions of respective software modules to determine whether the new software module is compatible with the existing set of software modules; and testing the new software module in a test data processing system in combination with the existing set of software modules in response to a negative determination.

Maintaining and testing a software application by performing regression testing uses standard reusable test cases from change history records to generate actual test cases. A new test case template is created upon saving a change history entry. A subset of the actual and new test cases is determined, and new actual test cases generated and documented from the subset. The new actual test cases are released after successful verification.

A system including a vendor computer system. The vendor computer includes a test controller and a resource controller. The test controller is configured to provide a central access point to the vendor computer system and to manage test cases. The resource controller is configured to control testing of software products. The resource controller allocates cloud resources in a cloud network to test the software products via the test case.

Techniques for gathering and tracking build information are described. Builds are registered initially. When a test execution is performed, a matching build is automatically determined from those previously registered builds as matching the software under test for a particular session. This information is tabulated in a database in accordance with additional software and hardware or platform information describes the environment in which a program executes. The platform information includes software component information and system configuration information uniquely identifying a particular instance of an environment. Data stored in the database is then analyzed and available for performing queries, for example, such as regarding code volatility and determining testing associated with a particular build.

Disclosed is a method for using source code to create the models used in model-based testing. After exploring the intended behavior of a software package, a test engineer writes source code to model that intended behavior. The source code is compiled into a model, and the model is automatically analyzed to generate numerous test scripts that can exercise the behavior of the software package. When the tests are run, their results are compared against intended behaviors, and discrepancies are used to correct the software package (or to correct the source-code model if it was prepared incorrectly). The model coding, test generation, test execution, and comparison steps are repeated as often as necessary to thoroughly test the software package. In some embodiments, the test scripts generated by the model are written in XML (Extensible Markup Language), allowing the easy integration of the test scripts with a number of XML-based tools.

A system is disclosed for converting a source software script from one format into a target software script having another format. The process includes for converting both a script file for testing a software application as well as GUI files related to a user interface of the software application to be tested. The conversion can be performed automatically, or in a partially automatic fashion. If less than the entire software script is converted, corrections to the target script can be performed automatically

Some embodiments of the present invention provide a system that tests a software program. During operation, the system creates a behavioral model of the software program using branches, decisions, and options. Next, the system applies a weight assignment technique to the behavioral model to create a set of global identifiers (IDs), which correspond to test cases of the behavioral model. The system then generates a test case from the behavioral model and executes the test case on the software program. Finally, the system analyzes an output of the executed test case to determine a validity of the software program.

An intelligent test system for testing software code is provided. The intelligent system includes a profiled software component, a test executor, a database, a database updater, and a data analyzer / optimizer. The test executor creates a coverage data by using the profiled software component to execute a plurality of test cases of a test suite. The database stores the coverage data and the database updater is configured to store the coverage data into the database. The data analyzer / optimizer analyzes the coverage data contained in the database to find test cases affected by a modification to the software code. The data analyzer / optimizer also optimizes the test cases affected by the modification by selecting fewer test cases that satisfy a criteria. The test executor uses the test cases that satisfy the criteria to test the modification to the software code.