258 results about "Test plan" patented technology

A system and method for testing at least one application is provided. The system comprises a test plan or script creation module for enabling a user to create at least one test plan or script for use in testing the at least one application. The system also comprises a test results module for initiating and determining test results associated with testing of the at least one application according to the at least one test plan or script. In some embodiments, the test results module determines: (1) baseline test results achieved by resolving the at least one test plan or script against the at least one application prior to the application being put to actual use, and (2) dynamic test results achieved by resolving the at least one test plan or script against the at least one application after the at least one application has been put to actual use. The system may also include a comparison module for comparing the dynamic test results with the baseline test results.

A method, apparatus, article of manufacture, and a memory structure for generating a test code for an automatic procedure is disclosed. The method comprises the steps of defining a source file having a plurality of tags associated with a member of a library of executable code objects defining a set of instructions for performing a portion of the automatic test procedure, generating a test plan in a conventional language from the source file, and generating an automated test code for the automated test procedure from the source file. In one embodiment, a test index identifying system elements tested by the test code is generated and incorporated into the test plan, allowing the user to verify that all desired system elements are exercised by the automated test code. The article of manufacture comprises a data storage device tangibly embodying instructions to perform the method steps described above. The apparatus comprises means for defining a source file having a plurality of tags, wherein each tag is associated with a member of a library of executable code objects defining a set of instructions for performing a portion of an automatic test procedure, means for generating a test plan in a conversational language from the source file, and means for generating an automated test code for the automatic test procedure from the source file.

A method and system for well test optimization provides test parameters and variation range therefor, independently from preliminarily reservoir and downhole fluid data; and repeatedly executes the test for each parameter to obtain real-time measured data, and interpreted data that is compared to the variation range for meeting a test objective. A method and system for well test design and interpretation, includes a testing manager having testing hardware/gauge metrology; a geological model; dynamic/static engineering data acquisition; and a reservoir model generator. A method and system for well test design and interpretation generates a test plan and an initial reservoir model and data from real/near-real-time, surface/downhole/manual data, aggregated data based on quality control/assurance, and optimization data based thereon and simulated downhole data; models/interprets the optimization data to meet test objectives for terminating/continuing the test plan; modifies the optimization; and/or generates reports from the modeling/interpretation when terminating the test plan.

A software application is certified prior to deployment. A reviewer is assigned and a review time scheduled. A readiness assessment is performed prior to the review time. The reviewer then conducts a review including an overview, process flows identifying control points, deliverables, a demonstration, and a test plan. Results of the review are reported and a determination made of whether to certify the application. The software application may also be certified including performing additional testing after deployment.

Various embodiments include at least one or systems, methods, and software providing abilities to automatically generate a test plan that mitigates risk involved in testing less than an entirety of a software system following modification. Some embodiments operate to allow a user to influence the scope of an optimized test plan while also reducing a number of tests and test execution effort involved. Such embodiments may identify portions of the software system to test and portions of the software system that will not be tested in a manner that reduces a total testing effort involved. Reductions in testing effort are performed in generation of the test plan in view of testing preferences which are utilized not only to reduce the total effort in executing a test plan, but also does so to optimize the test plan.

A method for facilitating the management of a test process is proposed. For this purpose, the different test scenarios included in the process and their execution dependencies are represented by means of a customized UML activity diagram (300a). An execution weight is also associated with each test scenario (for example, defined by the man-hours required for its execution). In this way, it is possible to identify critical test scenarios (315g), which may impair the execution of the whole test process when they fail (because many other test scenarios depend on their successful completion). The order of execution of the test scenarios is then arranged into a test plan, so as to minimize the time required to reach the critical test scenarios. Preferably, the same process is repeated whenever any runtime condition changes (such when a test scenario fails).

A method for managing software life cycle is provided. The method provides a multi-user distributed environment supporting the proactive management of a software life-cycle for at least one stakeholder. The method includes the steps of: obtaining and analyzing requirement information, generating test plans, creating WBS documents, storing and managing life cycle historical information, supplying online workflow-based notifications and messages and providing role-based customized functionality.

A method for predicting performance of an application software under production environment based on low-end stimulation environment performance test and capacity planning comprises the following steps: establishing a service load model of an application software to be tested according to service load information; converting the service load model of the application software to be tested to a service load pressure model of the application software based on Little law; making a performance test plan of the application software under a low-end stimulation environment according to the service load pressure model of the application software and a deduced scene; carrying out the performance test of the application software by stimulating the pressure of a real service load under the low-end stimulation environment and collecting performance data of the application software; and inputting the performance data of the application software into a capacity planning tool and predicting the performance of the application software under the production environment based on the capacity planning prediction.

An electronic arrangement for analyzing a model-based testing scenario relating to a system under test (SUT), includes a model handler entity for obtaining and managing model data indicative of a model intended to exhibit the behavior of the SUT, a test plan handler entity for obtaining and managing test plan data indicative of a number of test cases relating to the model and expected outcome thereof, a test execution log handler entity for obtaining and managing test execution log data indicative of the execution of the test cases by the test executor and/or SUT, a communications log handler entity for obtaining and managing communications log data indicative of message traffic between the test executor entity and SUT, and an analyzer entity for detecting a number of failures and their causes in the model-based testing scenario on the basis of model, test plan, test execution log and communications log data.

The present invention is directed to an online product validation solution integrating an online testing module configured to assist a user to create test cases and a remote test automation module configured to execute the created test cases on remote test systems. When a user creates a test plan, complete test coverage for the test plan may be ensured and cross-checked with product specifications stored in the knowledge database. Moreover, seamless integration of the online testing module and the remote test automation module may provide a uniform interface for generating both manual and automated test cases. Test case status is reported within the test plan in synchronicity with test case execution.

A method includes creating a macro plan for a test project, creating a micro plan for the test project, wherein the micro plan and the macro plan are based on at least one common parameter, and reconciling the macro plan and the micro plan by identifying deviations between the macro plan and the micro plan based on the at least one common parameter.

Techniques are provided for testing new software slated to be deployed on a target machine population with a number of target machines having a number of existing software programs. Method steps can include obtaining a list of depending software programs on selected ones of the target machines. The list can include those of the existing software programs which depend on the new software and/or those of tile existing software programs on which the new software depends. The steps can further include identifying relevant test cases based on the list of depending software programs, instantiating a plurality of test client platforms characteristic of the target machine population, and testing the relevant test cases on the plurality of test client platforms to identify failures.

The invention relates to a risk based testing method. The risk based testing method comprises defining a process or system to be tested, identifying a plurality of risks associated with the process or system, quantifying each of the risks with a risk value, defining a test plan for the process or system, the test plan including a number of test cases, wherein testing of the test cases is prioritized based on the risk value, and executing the test plan. The invention also relates an article of manufacture. The article of manufacture comprises a computer useable medium having computer readable program code means embodied therein for testing a process or a system. The computer readable program code means in the article of manufacture comprises: computer readable program code means for causing the computer to receive and store data identifying a plurality of risks associated with the process or system; computer readable program code means for causing the computer to receive and store a risk value associated with each of the plurality of risks; computer readable program code means for causing the computer to receive and store data defining a test plan for the process or system, the test plan including at least one test case, the at least one test case comprising at least one step; computer readable program code means for causing the computer to receive and store data associating each of the plurality of risks with a step of a test case; and computer readable program code means for causing the computer to generate a report listing the risks in order of the risk value.

The present invention is directed to a system and method for a quality assurance tool generating test plans and identifying new test requirements for a new version of a product. Old versions of the product may be previously tested and test plan documents associated with previously tested versions of the product may be stored in a database. The database may store test plans, test configurations, test scopes, and the like for previously tested versions of the product. Product design requirements may be determined based on received customer desired features for the new version. The database may be updated by adding new tests for new features of the new version. A test plan document for the product may be generated based on the updated database. The generated test document may be verified through automatically generating a general test plan for the new version of the product by querying updated database with the product design requirements.

A process for generating a set of tests for a system includes identifying a plurality of factors to use in a design of experiments (DOE) test, using each of the plurality of factors in the DOE, identifying, through the DOE testing, one or more factors which have a significant effect an output of the system, including only the one or more factors in a Combinatorial design methodology (CDM) and generating a first test matrix based upon the CDM using the DOE inputs. The unique part of the process is then adding interactions of order greater than 2-way, as identified by the DOE, to the CDM matrix thus creating an optimized set of test cases. By using the sensitivity output of the DOE as an input to the final test matrix from the CDM, an affordable yet comprehensive test approach is provided.