VALIDATING SOFTWARE CHARACTERISTICS
First Claim
Patent Images
1. A method implemented at least in part by a computer, the method comprising:
- obtaining one or more logs generated in conjunction with executing code;
within the one or more logs, locating a start event record of a test scenario that is identified by an identifier, the start event record indicating a start timestamp and the identifier of the test scenario;
within the one or more logs, locating an stop event record of the test scenario, the stop event record indicating a stop timestamp and the identifier that identifies the test scenario;
identifying scenario records included in the one or more logs, the scenario records corresponding to log statements generated after the start event record and before the stop event record; and
using the scenario records to determine statistics regarding the test scenario, the statistics including at least one or more of;
performance and memory usage.
3 Assignments
0 Petitions
Accused Products
Abstract
Aspects of the subject matter described herein relate to software validation. In aspects, code may be instrumented to generate certain records upon execution. The code may be further instrumented to generate start and stop records that correspond to the start and stop events of a scenario of a program. The start and stop event records allow correlation of the scenario with other records written to the log. With the correlation and appropriate instrumentation, a tool may determine performance, memory usage, functional correctness, and other characteristics of program at the granularity of the scenario.
57 Citations
20 Claims
-
1. A method implemented at least in part by a computer, the method comprising:
-
obtaining one or more logs generated in conjunction with executing code; within the one or more logs, locating a start event record of a test scenario that is identified by an identifier, the start event record indicating a start timestamp and the identifier of the test scenario; within the one or more logs, locating an stop event record of the test scenario, the stop event record indicating a stop timestamp and the identifier that identifies the test scenario; identifying scenario records included in the one or more logs, the scenario records corresponding to log statements generated after the start event record and before the stop event record; and using the scenario records to determine statistics regarding the test scenario, the statistics including at least one or more of;
performance and memory usage. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
-
-
12. In a computing environment, a system, comprising:
-
a memory structured to store logs generated in conjunction with executing code; and an analyzer coupled to the memory, the analyzer implemented via one or more processors, the analyzer structured to perform actions, the actions comprising; obtaining one or more logs from the memory, within the one or more logs, locating a start event record of a test scenario that is identified by an identifier, the start event record indicating a start timestamp and the identifier of the test scenario, within the one or more logs, locating a stop event record of the test scenario, the stop event record indicating a stop timestamp and the identifier that identifies the test scenario, identifying scenario records included in the one or more logs, the scenario records having timestamps after the start timestamp and before the stop timestamp, and using the scenario records to determine whether memory usage for the scenario has followed a hint associated with the scenario. - View Dependent Claims (13, 14, 15, 16, 17, 18, 19)
-
-
20. A computer storage medium having computer-executable instructions, which when executed perform actions, comprising:
-
sending a request for an analysis report to an analysis system that is structured to generate the analysis report by actions including; obtaining one or more logs generated in conjunction with executing code of a test scenario, locating a start event record and a stop event record within the logs, the start event record indicating a start timestamp of the test scenario, the stop event record indicating a stop timestamp of the test scenario, identifying scenario records included in the one or more logs, the scenario records having timestamps after the start timestamp and before the stop timestamp, using the scenario records to determine at least performance and memory usage statistics regarding the test scenario; and from the analysis system, receiving a report that includes the statistics.
-
Specification