Indicating a readiness of a change for implementation into a computer program
US-2016026554-A1 · Jan 28, 2016 · US
US10122866B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10122866-B2 |
| Application number | US-201615256123-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 2, 2016 |
| Priority date | Sep 2, 2016 |
| Publication date | Nov 6, 2018 |
| Grant date | Nov 6, 2018 |
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 is disclosed. The method includes generating a set of test case tags that describe attributes included in a test case and store the set of test case tags and the test case, receiving input information, and dynamically generating a test suite of one or more test cases based on input attributes data included in the input information, wherein the input information comprises code change information.
Opening claim text (preview).
What is claimed is: 1. A printer test system comprising: a memory to store: tag generation logic; test suite generation logic; and a test driver; and a processor to execute: the tag generation logic to receive print job data as a test case, and parse the print job data to generate a set of test case tags that describe attributes of the print job data to be included in the test case and store the set of test case tags and the test case; the test suite generation logic to receive input information, and dynamically generate a test suite of one or more test cases to test a printing system based on input attributes included in the input information, wherein the input information comprises code change information; and the test driver to execute a test suite. 2. The system of claim 1 , wherein the test suite generation logic comprises test case selection logic to select one or more test cases to test one or more attributes indicated in the input information. 3. The system of claim 2 , wherein the test suite generation logic further comprises a parser to parse the input information to acquire the input attributes included in the input information. 4. The system of claim 1 , wherein the input information further comprises at least one of: issue information and user input information. 5. The system of claim 3 , wherein the test case selection logic gathers one or more test cases based on a match between input attributes included in the input information and a tag within the set of tags corresponding to the one or more test cases. 6. The system of claim 5 , wherein the test case selection logic filters the test cases to determine valid test cases. 7. The system of claim 6 , wherein the test case selection logic orders the test cases into an ordered list based on a priority. 8. The system of claim 7 , wherein the priority of the ordered list is based upon user criteria. 9. The system of claim 8 , wherein the user criteria comprises at least one or more of: a user selected confidence level and a user selected execution time period. 10. The system of claim 8 , wherein the test case selection logic generates the test suite based on the priority of the ordered list. 11. The system of claim 10 , wherein the test case selection logic determines whether the user criteria has been met prior to execution of the test suite. 12. The system of claim 1 , wherein the test case comprises: a job ticket; and a page description language (PDL) datastream. 13. The system of claim 12 , wherein the tag generation logic parses the job ticket to generate a set of tags and store the test case and the set of tags. 14. The system of claim 1 , wherein the test case selection logic reorders the test cases in the test suite prior to execution of the test suite. 15. The system of claim 14 , wherein the test case selection logic reorders the test cases in the test suite to maintain test priority and consecutively execute test cases having identical configuration information.
resulting in reduced user or operator actions, e.g. presetting, automatic actions, using hardware token storing data · CPC title
achieving increased printing speed, i.e. reducing the time between printing start and printing end · CPC title
Automatic configuration, e.g. by driver · CPC title
based on job priority, e.g. re-arranging the order of jobs, e.g. the printing sequence · CPC title
Software or firmware update, e.g. device firmware management · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.