System and method for software test analysis
US-2024419581-A1 · Dec 19, 2024 · US
US9785542B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9785542-B2 |
| Application number | US-201313864191-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 16, 2013 |
| Priority date | Apr 16, 2013 |
| Publication date | Oct 10, 2017 |
| Grant date | Oct 10, 2017 |
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.
A method for debugging test procedures for automated device testing is disclosed. The method comprises receiving a command to update at least one modified test procedure modified during a first debugging session and saving state information for a test plan, wherein the state information comprises information regarding a breakpoint entry location, and wherein the modified test procedure is invoked within the test plan. The method subsequently comprises suspending execution of the test plan and unloading the modified test procedure. It also comprises compiling the modified test procedure to produce a compiled file and then reloading the test procedure into the test plan using the compiled file. Finally, it comprises resuming execution of the modified test procedure in a second debugging session and breaking the execution during the second debugging session at a breakpoint corresponding to the breakpoint entry location.
Opening claim text (preview).
What is claimed is: 1. A computer implemented method for debugging test procedures for automated device testing, said method comprising: receiving a command to update and invoke modifications made to at least one modified test procedure, wherein said at least one modified test procedure is modified during a first debugging session; saving state information for a test plan, wherein said state information comprises information regarding a breakpoint entry location, wherein said modified test procedure is invoked within said test plan, wherein said test plan is operable to execute on a site controller connected to plurality of devices under test (DUT), and wherein said test plan comprises a sequence of tests operable to be applied said plurality of DUTs coupled to automated test equipment, and wherein each test procedure is operable to implement a type of test applied to said plurality of DUTs; suspending execution of said test plan; unloading said modified test procedure from said test plan, wherein said unloading comprises detaching a debugger executing said first debugging session from said site controller; compiling said modified test procedure to produce a compiled file associated with said modified test procedure; reloading said modified test procedure into said test plan using said compiled file, wherein said reloading comprises attaching said debugger to said site controller and wherein said reloading further comprises transferring said compiled file from a system controller to said site controller, wherein said system controller is communicatively coupled to said site controller and wherein said system controller controls said site controller and instantiating test instances associated with said modified test procedure in said test plan using said compiled file; resuming execution of said modified test procedure and said test plan in a second debugging session; and breaking said execution during said second debugging session at a breakpoint corresponding to said breakpoint entry location, wherein said saving, said suspending, said unloading, said compiling, said reloading, said resuming and said breaking occur automatically in response to said receiving. 2. The method of claim 1 , wherein said resuming further comprises: clearing prior breakpoints set during said first debugging session; setting a breakpoint in said modified test procedure corresponding to said breakpoint entry location; and restoring said prior breakpoints after execution breaks during said second debugging session at said breakpoint corresponding to said breakpoint entry location. 3. The method of claim 1 , wherein said reloading further comprises: populating said test instances in said test plan with parameter values originally set during said first debugging session. 4. The method of claim 1 , wherein said modified test procedure comprises a base test procedure and at least one derived test procedure that depends from said base test procedure. 5. The method of claim 4 , further comprising: identifying said at least one derived test procedure that depends from said base test procedure before said unloading. 6. The method of claim 1 , further comprising: executing said modified test procedure to completion prior to said suspending. 7. The method of claim 1 , wherein said breakpoint entry location is selected from the group comprising: a current line, beginning of a current function, and any prior breakpoints. 8. The method of claim 1 , further comprising: executing said test plan to completion from said breakpoint corresponding to said breakpoint entry location during said second debugging session. 9. The method of claim 1 , further comprising: invoking said command to update said modified test procedure automatically when said modified test procedure is modified and a debug command is executed. 10. The method of claim 1 , further comprising: determining if test procedures are running in parallel to said modified test procedure in concurrently executing branch flow items; executing said test procedures running in parallel to completion while said modified test procedure is in a suspended state following said suspending; and suspending execution of further test procedures in said concurrently executing branch flow items while said modified test procedure is executing. 11. A non-transitory computer-readable storage medium having stored thereon, computer executable instructions that, if executed by a computer system cause the computer system to perform a computer implemented method for debugging test procedures for automated device testing, said method comprising: receiving a command to update and invoke modifications made to at least one modified test procedure, wherein said at least one modified test procedure is modified during a first debugging session; saving state information for a test plan, wherein said state information comprises information regarding a breakpoint entry location, wherein said modified test procedure is invoked within said test plan, wherein said test plan is operable to execute on a site controller connected to plurality of devices under test (DUT), and wherein said test plan comprises a sequence of tests operable to be applied said plurality of DUTs coupled to automated test equipment, and wherein each test procedure is operable to implement a type of test applied to said plurality of DUTs; suspending execution of said test plan; unloading said modified test procedure from said test plan, wherein said unloading comprises detaching a debugger executing said first debugging session from said site controller; compiling said modified test procedure to produce a compiled file associated with said modified test procedure; reloading said modified test procedure into said test plan using said compiled file, wherein said reloading comprises attaching said debugger to said site controller and wherein said reloading further comprises transferring said compiled file from a system controller to said site controller, wherein said system controller is communicatively coupled to said site controller and wherein said system controller controls said site controller and instantiating test instances associated with said modified test procedure in said test plan using said compiled file; resuming execution of said modified test procedure and said test plan in a second debugging session; and breaking said execution during said second debugging session at a breakpoint corresponding to said breakpoint entry location, wherein said saving, said suspending, said unloading, said compiling, said reloading, said resuming and said breaking occur automatically in response to said receiving. 12. The non-transitory computer-readable storage medium as described in claim 11 , wherein said method further comprises: clearing prior breakpoints set during said first debugging session; setting a breakpoint in said modified test procedure corresponding to said breakpoint entry location; and restoring said prior breakpoints after execution breaks during said second debugging session at said breakpoint corresponding to said breakpoint entry location. 13. The non-transitory computer-readable storage medium as described in claim 11 , wherein said method further comprises: populating said test instances in said test plan with parameter values originally set during said first debugging session. 14. The non-transitory computer-readable storage medium as described in claim 11 , wherein said modified test procedure comprises a base test procedure and at least one derived test procedure that depends from said base test procedure. 15. T
Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing · CPC title
for test execution, e.g. scheduling of test suites · CPC title
Generation of test inputs, e.g. test vectors, patterns or sequences {; with adaptation of the tested hardware for testability with external testers} · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.