Scenario based stress testing

• US 20060129892A1
• Filed: 11/30/2004
• Published: 06/15/2006
• Est. Priority Date: 11/30/2004
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Diaconu, Claudiu G., Govreau, Eric J., Qian, Zhenrong
• Application Number:
  US11/000,274
• Publication Number:
  US 20060129892A1
• Time in Patent Office: Days
• US Class Current: 714/38
• CPC Class Codes: G06F 11/3672 Test management

Abstract

The subject invention relates to systems and methods for automatically testing and stressing computer components on a plurality of computer systems. In one aspect, a system is provided to facilitate software testing of a computing environment. The system includes one or more profiles that describe software actions related to operations of a computing system, wherein the actions can be specified from usage data gathered or modeled from various sources. A weighting component specifies likelihoods of the software actions in order to more closely test or model actual operations of the computing system, whereby a test selection module employs the likelihoods to determine software tests that exercise the software actions in order to predict future behavior of the computing system.

Claims

1. A system to facilitate software testing of a computing system, comprising:

at least one profile to describe software actions related to operations of a computing system; and

a weighting component to specify likelihoods of the software actions in order to test the operations of the computing system.

2. The system of claim 1, further comprising a test selection module that determines at least one software test that exercises the software actions in order to predict future behavior of the computing system.

3. The system of claim 2, further comprising a test harness to execute the software tests on one or more target systems.

4. The system of claim 2, further comprising a database to log performance data from the software tests.

5. The system of claim 4, further comprising one or more reliability models that are applied to the performance data in order to predict future computing system performance.

6. The system of claim 1, the profile includes a list of repetitive actions a customer or machine performs when a software product is executed.

7. The system of claim 6, the actions are specified with a repetition rate describing how often a particular action occurs.

8. The system of claim 2, the test selection module executes a set of tests or components that implement or simulate the software actions defined in the profiles.

9. The system of claim 8, the tests are queued for execution at random or predetermined times by the test selection module, wherein a test harness performs test execution by loading the tests on clients and/or server systems.

10. The system of claim 1, further comprising a reporting website to gather performance data from tests or determine reliability estimates from models.

11. The system of claim 1, the weighting component defines or determines a relative weight that is calculated for one or more software actions defined in the profile based on a frequency of the actions and a frequency of other actions listed in the profile.

12. The system of claim 1, further comprising a component to log positive or negative results, event log errors, and debugger breaks.

13. The system of claim 1, further comprising a controller that runs a plurality of software tests that implement or mimic customer or machine actions.

14. The system of claim 1, the profile is derived from marketing data, industry data, or monitored data.

15. The system of claim 1, the weighting component is associated with weighting criteria to assign a given likelihood for a software action specified in the profile, wherein the weighting criteria is derived from frequency or repetition rates of a software action, mathematical or reliability models, from previously detected patterns of usage, or from empirical analysis of typical or worst case system usage.

16. The system of claim 1, further comprising a user interface to setup a server system, a client system, or a driver.

17. The system of claim 16, the user interface includes components for starting a server, configuring hardware, installing test modules to exercise software actions, configuring including printers, adding users, adding computers, adding connections to the Internet, configuring machines for remote access, configuring monitoring components for test performance, or configuring back-up servers and clients.

18. The system of claim 16, the user interface includes components for installing operating system components, installing test harness components, copying files, running a test setup component, configuring a data source administrator, or running a test harness.

19. The system of claim 16, the user interface includes components for creating user accounts, creating mailboxes for users, creating folders for users, adding users to security groups, adding users to distribution groups, configuring server access for users, setting up client computers for users, setting up network connections, setting up node and domain names, setting up connection types, configuring firewalls, setting up security configurations, setting up virtual private networks, or configuring alert messages and times.

20. A computer readable medium having computer readable instructions stored thereon for implementing the components of claim 1.

21. A system for exercising a networked computer system, comprising:

means for gathering customer or machine software usage data;

means for assigning weights to the usage data;

means for selecting tests that simulate actions relating to the usage data; and

means for executing the tests.

22. The system of claim 21, further comprising means for applying reliability predictions to the usage data.

23. A method for automatically testing and exercising computer systems, comprising:

describing machine or customer actions in a user profile;

automatically assigning a frequency to the customer actions;

designing software tests for the customer actions;

loading the software tests on a client, a server, or a stand-alone machine; and

executing the software tests from a remote location in accordance with the frequency of the customer actions.

24. The method of claim 23, further comprising executing the software tests in a random or a pre-determined manner.

26. The method of claim 23, further comprising automatically logging performance data for the performance tests and applying reliability models to the performance data to predict future system performance.

25. The method 23, further comprising executing the software tests in accordance with a test block, wherein the test block is associated with a single user profile.

27. A system to exercise networked software components, comprising:

a plurality or user profiles modeling user or machine software actions;

a frequency component to define a rate for the software actions;

a test selection module to select tests that exercise the software actions;

a test harness controller to execute the tests on a plurality of computers in a random manner;

a website to log performance data from the tests; and

at least one reliability model to analyze the performance data.