System and method for software test analysis
US-2024419581-A1 · Dec 19, 2024 · US
US2016246708A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2016246708-A1 |
| Application number | US-201315028758-A |
| Country | US |
| Kind code | A1 |
| Filing date | Oct 30, 2013 |
| Priority date | Oct 30, 2013 |
| Publication date | Aug 25, 2016 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Recording an application test can include creating a number of recordings that define a number of interactions with an application under test (AUT), wherein the number of recordings are created serially. Recording an application test can include replaying each of the number of recordings while the number of recordings are being created to determine an outcome of a test. Recording an application test can include analyzing and reporting the outcome of the test.
Opening claim text (preview).
What is claimed: 1 . A non-transitory machine-readable medium storing instructions for recording an application test executable by a machine to cause the machine to: create a number of recordings that define a number of interactions with an application under test (AUT), wherein the number of recordings are created serially; replay each of the number of recordings while the number of recordings are being created to determine an outcome of a test; and analyze and report the outcome of the test. 2 . The medium of claim 1 , wherein the instructions are executable to initialize a number of resources that enable a replay of each of the number of recordings. 3 . The medium of claim 2 , wherein the number of resources are initialized before a creation of the number of recordings. 4 . The medium of claim 2 , wherein the number of recordings are initialized before the replay of the number of recordings. 5 . The medium of claim 1 , wherein the instructions executable to create the number of recordings include instructions to create the number of recordings by dividing a recording based on a number of rules. 6 . The medium of claim 1 , wherein the instructions executable to create the number of recordings include instructions to create the number of recordings based on a number of inputs provided by a user that signal a beginning and an end for each of the number of recordings. 7 . A system for recording an application test comprising a processing resource in communication with a non-transitory machine readable medium having instructions executed by the processing resource to implement: a record engine to create a number of recordings that define a number of interactions with an application under test (AUT), wherein the number of recordings are created serially; a replay engine to begin a concurrent replay of each of the number of recordings on a number of different platforms, wherein the concurrent replay is begun in between a creation of the number of recordings; and an analyze engine to analyze and report a number of outcomes of a number of portions of a test that are associated with the number of recordings. 8 . The system of claim 7 , including instructions to analyze and report the number of outcomes of the number of portions of the test after the concurrent replay of an associated recording. 9 . The system of claim 8 , including instructions to analyze and report the number of outcomes of the number of portions of the test before a recording phase is terminated wherein a recording phase includes a creation of the number of recordings. 10 . The system of claim 7 , including instructions to recommend a solution for each of the number of portions of the test that failed wherein a number of recommendations are given while the number of recordings are being created. 11 . A method for recording an application test comprising: creating a number of recordings that define a number of interactions with an application under test (AUT), wherein the number of recordings are created serially; beginning a number of concurrent replays of the number of recordings on a number of different platforms, wherein each of the number of concurrent replays is begun after a corresponding recording is created and before a different recording is created; analyzing and reporting an outcome of a test; providing a number of solutions for a number of failed portions of the test; and beginning a number of concurrent replays of the number of recordings that are associated with the number of failed portions of the test after the number of solution are provided. 12 . The method of claim 11 , wherein the method includes serially providing the number of solutions. 13 . The method of claim 12 , wherein each of the number of concurrent replays of the number of recordings that are associated with the number of failed portions of the test begins after a corresponding solution is provided. 14 . The method of claim 13 , wherein each of the number of concurrent replays of the number of recordings that are associated with the number of failed portions of the test begin before a solution for a different failed portion of the test is provided. 15 . The method of claim 14 , wherein beginning the number of concurrent replays of the number of recordings that are associated with the number of failed portions of the test includes hosting the number of concurrent replays and the number of different platforms on a number of different computing devices.
tracing values on a bus · CPC title
Environments for analysis, debugging or testing of software · CPC title
for test execution, e.g. scheduling of test suites · CPC title
Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation {; Recording or statistical evaluation of user activity, e.g. usability assessment} · CPC title
Data logging (G06F11/14, G06F11/2205 take precedence) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.