Abstract: Examples of techniques for function modification for software application testing are described herein. An aspect includes, based on a function call to a function by an application under test that is being tested using a test case in a testing environment, determining whether modification of the function is enabled. Another aspect includes, based on determining that modification of the function is enabled, running the function in a modified mode.

Abstract: Interrupt code conversion for efficient computer program recovery. In response to an error being detected while processing instructions of a computer program running on a computer system, the OS receives a first program interrupt code (PIC) and interrupts the computer program. Control of the computer program is passed to a program interrupt handler and the program interrupt handler inspects the first PIC issued as a result of detecting the error. The first PIC is converted to a second PIC wherein the second PIC is associated with another error predicted when subsequent running of the computer program occurs. The second PIC is presented to a recovery routine associated with the computer program and, in response to the detected error, running of the computer program is customized based on the second PIC rather than the first PIC.

Abstract: Examples of techniques for environment modification for software application testing are described herein. An aspect includes, based on starting testing of an application under test using a test case in a testing environment and determining that modification of the testing environment is enabled, modifying the testing environment. Another aspect includes running the testing of the application under test using the test case in the modified testing environment. Another aspect includes, based on detection of an error during the testing of the application under test, determining whether the error was caused by the modified testing environment. Another aspect includes, based on determining that the error was caused by the modified testing environment, suppressing the error and continuing the testing of the application under test in the modified testing environment. Another aspect includes, based on determining that the error was not caused by the modified testing environment, percolating the error.

Abstract: Systems, methods, and computer-readable media are described for associating regression test cases with corresponding test fingerprints via a translation table or other suitable storage mechanism. A test fingerprint indicates a collection of breakpoints encountered as part of traversal of a code path during execution of a test case, and thus, provides an indication of an extent of code coverage of the test case. Test fingerprints can be evaluated to determine cumulative code coverage of sets of test cases. Specific sets of test cases can be selected based on the cumulative code coverage they provide. Sets of test cases that provide greater cumulative code coverage and/or that target specific areas of interest can be prioritized for execution particularly when having to adhere to execution constraints.

Abstract: Systems, methods, and computer-readable media are described for performing revision control for a System Under Test (SUT) such as a body of source code. Prior to committing code changes, a collection of breakpoints associated with the portion(s) of source code being changed are determined. Stored fingerprints corresponding to regression test cases are evaluated to identify a set of stored fingerprints that are cumulatively indicative of the collection of breakpoints. Attributes respectively stored in association with the set of stored fingerprints are determined and a corresponding group of regression test cases are determined. The code changes are committed responsive to successful execution of the selected group of regression test cases.

Abstract: Systems, methods, and computer-readable media are described for generating fingerprints for regression tests that identify code paths taken during execution of the regression tests. Breakpoint values are assigned to breakpoints encountered during execution of a regression test and a fingerprint is generated based on the assigned breakpoint values and a code path taken during execution of the regression test. Various breakpoint value assignment/fingerprint generation algorithms are described herein that generate a fingerprint from which a corresponding code path taken can be reconstructed including which breakpoints are encountered, the number of times each such breakpoint is encountered, and the order in which the breakpoints are encountered.

Abstract: Systems, methods, and computer-readable media are described for performing revision control for a System Under Test (SUT) such as a body of source code. Prior to committing code changes, a collection of breakpoints associated with the portion(s) of source code being changed are determined. Stored fingerprints corresponding to regression test cases are evaluated to identify a set of stored fingerprints that are cumulatively indicative of the collection of breakpoints. Attributes respectively stored in association with the set of stored fingerprints are determined and a corresponding group of regression test cases are determined. The code changes are committed responsive to successful execution of the selected group of regression test cases.

Abstract: Systems, methods, and computer-readable media are described for generating fingerprints for regression tests that identify code paths taken during execution of the regression tests. Breakpoint values are assigned to breakpoints encountered during execution of a regression test and a fingerprint is generated based on the assigned breakpoint values and a code path taken during execution of the regression test. Various breakpoint value assignment/fingerprint generation algorithms are described herein that generate a fingerprint from which a corresponding code path taken can be reconstructed including which breakpoints are encountered, the number of times each such breakpoint is encountered, and the order in which the breakpoints are encountered.

Abstract: Systems, methods, and computer-readable media are described for associating regression test cases with corresponding test fingerprints via a translation table or other suitable storage mechanism. A test fingerprint indicates a collection of breakpoints encountered as part of traversal of a code path during execution of a test case, and thus, provides an indication of an extent of code coverage of the test case. Test fingerprints can be evaluated to determine cumulative code coverage of sets of test cases. Specific sets of test cases can be selected based on the cumulative code coverage they provide. Sets of test cases that provide greater cumulative code coverage and/or that target specific areas of interest can be prioritized for execution particularly when having to adhere to execution constraints.

Abstract: Interrupt code conversion for efficient computer program recovery. In response to an error being detected while processing instructions of a computer program running on a computer system, the OS receives a first program interrupt code (PIC) and interrupts the computer program. Control of the computer program is passed to a program interrupt handler and the program interrupt handler inspects the first PIC issued as a result of detecting the error. The first PIC is converted to a second PIC wherein the second PIC is associated with another error predicted when subsequent running of the computer program occurs. The second PIC is presented to a recovery routine associated with the computer program and, in response to the detected error, running of the computer program is customized based on the second PIC rather than the first PIC.

Abstract: Examples of techniques for environment modification for software application testing are described herein. An aspect includes, based on starting testing of an application under test using a test case in a testing environment, determining whether modification of the testing environment is enabled. Another aspect includes, based on determining that modification of the testing environment is enabled, modifying the testing environment.

Abstract: Examples of techniques for function modification for software application testing are described herein. An aspect includes, based on a function call to a function by an application under test that is being tested using a test case in a testing environment, determining whether modification of the function is enabled. Another aspect includes, based on determining that modification of the function is enabled, running the function in a modified mode.

Abstract: Embodiments are provided for implementing a transparent conversion of common virtual storage requests to storage with limited access. Embodiments include providing a storage manager configured to perform address translation for requests, providing a data address translation (DAT) structure configured to connect a higher-level DAT table to a lower-level DAT table, and creating the DAT structure based on a request from a process. Embodiments also include responsive to receiving a storage request, performing a DAT fault process based on validating user credentials associated with an entry of the higher-level DAT table corresponding to the storage request, and responsive to the validation, updating the higher-level DAT table entry to allow access to the restricted-use portion of the common virtual storage, and otherwise, returning a DAT fault for the higher-level DAT table entry.