Automated operating system test framework

A system for automating testing of a first computing system comprising:

• a plurality of processors;
• an identifying component, executed on the plurality of processors, for identifying a plurality of system interface elements of a second computing system;
• a determining component, executed on the plurality of processors, for determining an untested state at said first computing system of one of said identified plurality of system interface elements;
• a determining component, executed on the plurality of processors, for determining the existence of any dependency of said one of said identified plurality of system interface elements upon another of said identified plurality of system interface elements;
• a seeking component, executed on the one or more processors, responsive to a finding of no said dependency for seeking in a repository a system interface element test corresponding to said one of said identified plurality of system interface elements and having an expected output according to a structure of said second computing system;
• an executing component, executed on the plurality of processors, for executing said system interface element test at said first computing system;
• a creator component, executed on the plurality of processors, responsive to a failure of said seeking to find a said system interface element test, for creating a new test corresponding to said one of said identified plurality of system interface elements;
• said executing component further adapted for executing said new test at said second computing system;
• and
• a storing component, executed on the plurality of processors, for storing in said repository said new test and an expected output corresponding to an output of said executing said new test at said second computing system.

A computer programming product, comprising:

• a non-transitory computer readable storage medium;
• and
• logic, stored on the computer readable storage medium for execution on a processor, for:
• identifying a plurality of system interface elements of a second computing system;
• determining an untested state at said first computing system of one of said identified plurality of system interface elements;
• determining the existence of any dependency of said one of said identified plurality of system interface elements upon another of said identified plurality of system interface elements;
• responsive to a finding of no said dependency, seeking in a repository a system interface element test corresponding to said one of said identified plurality of system interface elements and having an expected output according to a structure of said second computing system;
• executing said system interface element test at said first computing system;
• responsive to a failure of said seeking to find a said system interface element test, creating a new test corresponding to said one of said identified plurality of system interface elements;
• executing said new test at said second computing system;
• and
• storing in said repository said new test and an expected output corresponding to an output of said executing said new test at said second computing system.

A method of automating testing of a first computing system comprising:

• identifying a plurality of system interface elements of a second computing system;
• determining an untested state at said first computing system of one of said identified plurality of system interface elements;
• determining the existence of any dependency of said one of said identified plurality of system interface elements upon another of said identified plurality of system interface elements;
• responsive to a finding of no said dependency, seeking in a repository a system interface element test corresponding to said one of said identified plurality of system interface elements and having an expected output according to a structure of said second computing system;
• executing said system interface element test at said first computing system;
• comparing an output of said executing said system interface element test at said first computing system with said expected output in said repository;
• and
• responsive to a mismatch between said output of said executing and said expected output, eliciting a user input.

A system for automating testing of a first computing system comprising:

• a plurality of processors;
• an identifying component, executed on the plurality of processors, for identifying a plurality of system interface elements of a second computing system;
• a determining component, executed on the plurality of processors, for determining an untested state at said first computing system of one of said identified plurality of system interface elements;
• a determining component, executed on the plurality of processors, for determining the existence of any dependency of said one of said identified plurality of system interface elements upon another of said identified plurality of system interface elements;
• a seeking component, executed on the one or more processors, responsive to a finding of no said dependency for seeking in a repository a system interface element test corresponding to said one of said identified plurality of system interface elements and having an expected output according to a structure of said second computing system;
• a comparator component, executed on the one or more processors, for comparing an output of said executing said system interface element test at said first computing system with said expected output in said repository;
• and
• an input eliciting component, executed on the one or more processors, responsive to a mismatch between said output of said executing and said expected output, eliciting a user input.

A computer programming product, comprising:

• a non-transitory computer readable storage medium;
• and
• logic, stored on the computer readable storage medium for execution on a processor, for:
• identifying a plurality of system interface elements of a second computing system;
• determining an untested state at said first computing system of one of said identified plurality of system interface elements;
• determining the existence of any dependency of said one of said identified plurality of system interface elements upon another of said identified plurality of system interface elements;
• responsive to a finding of no said dependency, seeking in a repository a system interface element test corresponding to said one of said identified plurality of system interface elements and having an expected output according to a structure of said second computing system;
• executing said system interface element test at said first computing system;
• comparing an output of said executing said system interface element test at said first computing system with said expected output in said repository;
• and
• responsive to a mismatch between said output of said executing and said expected output, eliciting a user input.