VALIDATING SOFTWARE CHARACTERISTICS

• US 20150143180A1
• Filed: 11/21/2013
• Published: 05/21/2015
• Est. Priority Date: 11/21/2013
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Dawson, Ryan A., Chandnani, Dinesh B., Xing, Li
• Application Number:
  US14/086,862
• Publication Number:
  US 20150143180A1
• Time in Patent Office: Days
• US Class Current: 714/38.1
• CPC Class Codes: G06F 11/073 in a memory management context, e.g. virtual memory or cache management memory management G06F12/00; testing of static memory units G11C29/00
• CPC Class Codes: G06F 11/076 by exceeding a count or rate limit, e.g. word- or bit count limit
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 11/3612 by runtime analysis performance monitoring G06F11/3466
• CPC Class Codes: G06F 11/3636 by tracing the execution of the program

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.

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.

2. The method of claim 1, wherein obtaining one or more logs comprises obtaining one or more logs generated by one or more of instrumented:

application code, runtime code, rendering code, system code, and server code.

3. The method of claim 1, wherein identifying scenario records included in the one or more logs comprises finding records that have a process identifier and a thread identifier associated with the test scenario.

4. The method of claim 1, further comprising obtaining an analysis hint that indicates that the test scenario is expected to not have memory growth when repeated and highlighting output that indicates that memory consumption increased as the test scenario was repeated.

5. The method of claim 1, further comprising obtaining an analysis hint that indicates that the test scenario is expected to have constant duration when repeated and highlighting output that indicates that duration changed as the test scenario was repeated.

6. The method of claim 1, further comprising obtaining an analysis hint that indicates that the test scenario is expected to have variable duration and variable memory consumption when repeated and refraining from highlighting corresponding output that indicates variable duration and variable memory consumption as the test scenario was repeated.

7. The method of claim 1, wherein using the scenario records to determine statistics regarding the test scenario comprises using the scenario records to determine a duration of the test scenario.

8. The method of claim 1, wherein using the scenario records to determine statistics regarding the test scenario comprises using the scenario records to determine a delta of allocated memory before and after the test scenario.

9. The method of claim 1, wherein the statistics indicate delta allocated memory before and after the test scenario for two or more of:

application memory, runtime memory, rendering memory, system memory, and server memory.

10. The method of claim 1, further comprising outputting a graph that shows iterations of the scenario on one axis and memory allocated on another axis.

11. The method of claim 1, wherein using the scenario records to determine statistics regarding the test scenario comprises using the scenario records to determine a count of how many times the test scenario was executed.

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.

13. The system of claim 12, wherein the analyzer being structured to use the scenario records to determine whether memory usage for the test scenario has followed a hint associated with the test scenario comprises the analyzer being structured to perform actions comprising tracking memory used over a plurality of repetitions of the test scenario.

14. The system of claim 12, wherein the analyzer is further structured to perform additional actions, comprising using the scenario records to determine whether duration of executing the scenario has followed another hint associated with the scenario.

15. The system of claim 14, wherein the analyzer being structured to use the scenario records to determine whether duration of executing the scenario has followed another hint associated with the scenario comprises the analyzer being structured to perform actions comprising tracking duration of the test scenario over a plurality of repetitions of the test scenario.

16. The system of claim 12, further comprising a plurality of sources structured to write the logs to the memory while executing code associated with the test scenario.

17. The system of claim 16, wherein the sources comprise one or more processors structured to execute instrumented code, the instrumented code including one or more of:

application code, runtime code, rendering code, system code, and server code.

18. The system of claim 12, further comprising an output manager structured to output graph data that indicates iteration, delta memory usage per iteration, and a trend line of memory usage over iterations of the test scenario.

19. The system of claim 18, wherein the output manager is further structured to output table data that identifies at least the test scenario, whether the test scenario passed, a count of iterations of the test scenario, a maximum value, a mean value, and a standard deviation value associated with the iterations.

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.