Identifying a configuration element value as a potential cause of a testing operation failure
AssigneeEntit Software LLC
InventorsInbar Shani, Roy Nuriel, Amichai Nitsan
Life of this patent
Estimating the term…
Abstract
Examples disclosed herein relate to identifying a configuration element value as a potential cause of a testing operation failure. Examples include causing a testing operation to be performed approximately in parallel on each of a plurality of instances of an application executed in respective testing environments, acquiring configuration element values from each of the testing environments, and identifying at least one of the configuration element values as a potential cause of a testing operation failure.
Claims15
A non-transitory machine-readable storage medium comprising instructions that when executed by a processing resource of a computing device cause the processing resource to:
- cause a testing operation to be performed approximately in parallel on each of a plurality of instances of an application, each instance executed in a respective one of a plurality of testing environments having different configurations from one another;
- acquire, from each of the testing environments, configuration element values for the testing environment, the values defining the configuration of the testing environment;
- determine that the testing operation has failed at a first one of the testing environments and has passed at a second one of the testing environments;
- and
- in response to the determination, identify one of the configuration element values acquired from the first testing environment as a potential cause of the testing operation failure based on differences between the configuration element values acquired from the first testing environment and the configuration element values acquired from the second testing environment.
A system comprising:
- a processor;
- and
- a memory storing instructions that when executed by the processor cause the processor to:
- cause a mirror testing operation of a mirror testing process to be performed approximately in parallel on each of a plurality of instances of an application, each instance executed in a respective one of a plurality of testing environments having different configurations from one another;
- acquire, from each of the testing environments, configuration element values for the testing environment, the values defining the configuration of the testing environment;
- determine that the mirror testing operation has failed at a first one of the testing environments and succeeded at a second one of the testing environments;
- in response to the determination, compare the configuration element values for the first testing environment to the configuration element values for the second testing environment, respectively;
- and
- identify, as a potential cause of the mirror testing operation failure, one of the configuration element values acquired from the first testing environment that differs from the respective value of the same configuration element acquired from the second testing environment.
A method comprising:
- causing, by a processor of a computing device, a mirror testing operation to be performed in parallel on each of a plurality of instances of an application, wherein each instance is executed in a respective one of a plurality of testing environments having different configurations from one another;
- acquiring, from each of the testing environments, configuration element values for the testing environment, the values defining the configuration of the testing environment;
- determining, by the processor, that the mirror testing operation has failed at a first testing environment of the plurality of testing environments and has passed at a second testing environment of the plurality of testing environments;
- in response to the determination, identifying, as potential causes of the failure, a plurality of configuration element values acquired from the first testing environment that differ from the respective values of the same configuration elements acquired from the second testing environment;
- and
- ranking, by the processor, the identified configuration element values acquired from the first testing environment based on, for each of the identified values, a likelihood of the identified value being a cause of the failure.
Dependencies are inferred from the claim text.