Patent Application
20120030515
This description relates to software testing.
Software frequently requires testing in order to ensure that proper, desired, and complete functionality is being provided by the software. For example, it is common to test software during an installation or upgrade of the software, or when re-configuring, patching, or activating the software.
Automated software tests may be performed in order to test software in a fast, efficient, and cost-effective manner. For example, for software to be tested, known software inputs may be determined in conjunction with expected software outputs. Then, the known software inputs may be input into the software, and the actual software outputs may be compared against the expected software outputs, in order to test a correctness and stability of the software, and to identify potential malfunctioning aspects of the software.
However, in many cases, changes in the software to be tested, including the very changes which prompt the testing, may skew a result of the testing, because, e.g., the known software inputs may be partially or wholly invalid with respect to the thus-changed software. For example, if the tested software includes a graphical user interface (GUI) that has been updated to include a new field, but the known software inputs do not reflect the presence of such a new field, then the actual software outputs may include an error message which is not a part of the expected software outputs. Consequently, a software test engineer may erroneously believe that the tested software is malfunctioning. Moreover, even if the software engineer recognizes that the error lies in the testing configuration, e.g., of the software inputs, it may be difficult for the software engineer to correct the testing configuration.
According to one general aspect, a computer system may include instructions recorded on a non-transitory computer-readable storage medium and readable by at least one processor. The system may include an attribute collector configured to cause the at least one processor to collect an attribute set for each test entity of a plurality of test entities associated with a software test executed in a software environment, an attribute analysis signal handler configured to cause the at least one processor to receive an attribute analysis signal associated with a change in the software environment, and a view generator configured to cause the at least one processor to provide an attribute-based view associated with an affected attribute set associated with the change, the attribute-based view identifying an affected test entity that is affected by the change.
According to another general aspect, a computer-implemented method for causing at least one processor to execute instructions recorded on a computer-readable storage medium may include collecting an attribute set for each test entity of a plurality of test entities associated with a software test executed in a software environment, receiving an attribute analysis signal associated with a change in the software environment, and providing an attribute-based view associated with an affected attribute set associated with the change, the attribute-based view identifying an affected test entity that is affected by the change.
According to another general aspect, a computer program product tangibly embodied on a computer-readable medium may include instructions that, when executed, are configured to cause at least one processor to collect an attribute set for each test entity of a plurality of test entities associated with a software test executed in a software environment, receive an attribute analysis signal associated with a change in the software environment, and provide an attribute-based view associated with an affected attribute set associated with the change, the attribute-based view identifying an affected test entity that is affected by the change.
The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features will be apparent from the description and drawings, and from the claims.
In the example of
In
For the sake of example, the software environment 106 of
As referenced above, testing of the tested system 104 by the test management system 102 may proceed with input of test input data 112 into the software environment 106. For example, a test engineer may wish to use the test management system 102 in order to test an operation or functionality of the user interface 108. The user interface 108 may have a plurality of fields, forms, input/output elements, and various other functionalities known to be implemented by user interfaces. Consequently, the test management system 102 may provide test input data 112 into various input elements of the user interface 108, and may consequently receive test output data 114 associated with outputs of the user interface 108. As is generally known, the test management system 102 may therefore compare the test input data 112 with the test output data 114, using expected test output (not explicitly illustrated in the example of
Over time, the software environment 106 may undergo various types and extents of changes. For example, components of the software environment 106 (e.g., the user interface 108, or the API 110), may be updated, modified, reinstalled, or otherwise altered during a lifetime of the software environment 106. In further examples, components may be added to, or removed from, the software environment 106 (e.g., the API 110 may be added to the software environment 106 at a point in time). Various other substantial changes to and within the software environment 106 are, by themselves, well known to one of skill in the art, and are therefore are not expressed here in further detail, except as may be necessary or helpful in understanding operations of the system 100.
In executing testing of the software environment 106, the test management system 102 may deploy or otherwise use a plurality of test entities as part of a given test configuration(s), shown in the simplified example of
For example, during an example testing of the software environment 106, it may occur that a particular test script is used to define the test input data 112, to receive the test output data 114, and/or to execute a comparison of the actual test output data 114 with expected test output data. Consequently, such test scripts may be considered as examples of whole or partial test entities. Further, a particular testing scenario or test case may include a number of different variants of the same or similar underlying test script. Further, it may occur that the particular test script is configured to call or otherwise utilize one or more additional test scripts, so as to thereby execute a composite test case which includes a hierarchy or other linking of desired test scripts.
In other examples, test entities may be defined by, or with respect to, different versions of the test input data 112, and/or may be defined with respect to different examples of tested systems 104, and/or associated software environments 106. Other uses and contexts of the term test entity, and thus, of the test entity 116A and the test entity 116B shown in the example of
In the example of
For example, during a testing of the software environment 106, testing may occur with respect to both the user interface 108 and the API 110. The attributes 118 may thus be collected by the attribute collector 120 and grouped by the attribute aggregator 122 into a first group associated with the user interface 108, and into a second group associated with the API 110.
Of course, this is merely a simplified example, and in additional or alternative implementations, the attribute collector 120 and the attribute aggregator 122 may serve to collect various other types of attributes, and to perform various other types of grouping thereon, respectively. For example, such attributes may include user-specific data such as log-on language, date format, time format, decimal notation, or time zone, or may include names of graphical user interface (GUI) fields (and identification showing whether the field is mandatory or optional), versions of software components, and transaction attributes (e.g., authorization objects assigned to a transaction, the GUI availability of a transaction). Specific additional or alternative examples of such attributes and associated grouping are provided in more detail, below.
In the example of
As referenced above, over time, changes may occur within the software environment 106. Consequently, in the example of
As referenced above, and as illustrated in the example of
For example, as referenced above, an initial testing of the software environment 106 may occur, as executed by the test management system 102. Subsequently, a change may occur within the software environment 106, which may affect, e.g., the user interface 108. Consequently, during a second or other subsequent testing of the software environment 106 which occurs after such change has happened, it may occur that the test entity 116A is no longer configured properly to test the updated or otherwise changed functions of the user interface 108. As a result, during such a second or subsequent testing, an exception may occur in which an error message is reported to the test management system and received by the exception handler 128. Of course, virtually any known technique for recognizing or reporting such an error or other exception may be used in variations of the system 100 of
In the example of
More specifically, an attribute comparator 130 may be configured to retrieve the first version of the attribute set 124A associated with the initial testing, and to receive the second version of the attribute set 124A associated with the second or subsequent testing (or whatever partial portion thereof was able to be collected prior to the occurrence of the exception). A view generator 132 may thereafter be configured to output the two versions of the attribute set 124A, whereupon the test engineer may easily be able to determine particular attributes which were affected by the intervening change in software environment 106. Consequently, the test engineer may thereafter be enabled to identify and repair the associated test entity 116A which is associated with the identified (i.e., affected) attributes.
Of course, it may be appreciated that the above example represents an extremely simplified scenario in which only a minimal number or amount of test entities, attributes, attribute sets, and software entities are included. In more general or realistic examples, it may be appreciated that a large number of attributes may be collected, and that a similarly large number of test entities may be present within the test management system 102. Nonetheless, by collecting the attributes 118 into the grouped attribute sets 124 as described herein, the attribute comparator 130 may be able to provide a convenient comparison of the collected attributes, in a manner which facilitates identification of the objects or other elements of the software environment 106 which were affected by the intervening change within the software environment, so that, as a result, a corresponding test entity may itself also be quickly and efficiently identified.
In specific examples, the view generator 132 may simply provide the different versions of the attribute set(s) in alignment with one another, for identification of the test entity therefrom by the test engineer. In other examples, the attribute comparator 130 may be operable to provide, in conjunction with the view generator 132, a view of only those attributes which are candidates for being associated with the change in an underlying element of the software environment 106 and/or with a corresponding test entity. In still further environments, as described in detail below, an entity identifier 133 may be configured to actually output a specific identification of one or more of the test entities 116 affected by the intervening change in software environment 106.
In the example of the exception handler 128, it may occur that the software environment 106 experiences a change, and that, as described, a test engineer does not become aware of the change until a subsequent time at which the change affects a corresponding subsequent testing of the software environment 106. In other example implementations, however, the test management system 102 may be configured to receive, detect, or otherwise determine such changes, at a time of occurrence of the changes. Consequently, the test management system 102 may be configured to identify affected test entities, and execute any corresponding repairs thereof, potentially before commencement of any subsequent testing. As a result, the test management system 102 may minimize or avoid (i.e., preempt) testing stoppages associated with exceptions caused by such intervening changes.
In the example of
In additional or alternative implementations, a change event handler 138 may be configured to receive changes 134 in response to, or in conjunction with, publication or other transmission of the changes 134 by the software environment 106 and/or the testing system 104. For example, as described in detail below with respect to
Thus, in the above examples, and in other example implementations, it may occur that the attribute analysis signal handler 126 uses the attribute analysis signal in the form of the changes 134 which are received from the testing system 104. The attribute comparator 130 and/or the entity identifier 133 may thereafter analyze the changes 134 with respect to the attribute sets 124A, 124B, to ultimately identify an appropriate test entity of the test entities 116A, 116B that may be affected by the changes 134. In this way, it is apparent that the test engineer may become aware of affected test entities which may need to be repaired, replaced, updated, or otherwise modified in order to ensure a complete and correct testing of the software environment 106 in the future.
In the example of
In particular, as referenced above, the test management system 102 is configured to collect attribute sets 124A, 124B in conjunction with testing of the software environment 106 by corresponding test entities 116A, 116B. At a beginning of such test scenarios, the test engineer may be presented with the view 140 which includes a check box allowing the test engineer to indicate whether it is necessary for a test management system 102 to collect attributes during the upcoming testing of the software environment 106. Of course, the view 140 may include many and various other aspects and functionalities associated with designing and executing such tests of the software environment 106. In the simplified example of
For example, the test engineer may use the view 140 to collect attributes during an initial testing of the software environment 106, but may not necessarily collect such attributes during subsequent testing, unless and until the changes 134 are detected. At that time, the test engineer may execute a subsequent test during which attributes may be collected for use by the attribute comparator 130 and the entity identifier 133 in identifying any and all affected test entities. Similarly, the view 140 may be used to collect attributes during a testing which occurs in conjunction with or after detection of an exception that occurs during testing of the software environment 106 (e.g., as detected by the exception handler 128).
Meanwhile, the view 142 is intended to conceptually represent the various types and combinations of outputs which may be provided, e.g., by the attribute comparator 130 and/or the entity identifier 133. For example, as shown in the view 142, and as described above, the view generator 132 may output an attribute comparison which compares collected attributes during two separate or independent testings of the software environment 106, where it may be appreciated that the second testing occurs after an occurrence of at least one change to or within the software environment 106. In this way, as described, the test engineer may view such an attribute comparison and determine affected attributes, for use and thereby ultimately identifying corresponding affected test entities.
In addition to, or as an alternative to, the output of such output comparisons, the view 142 may simply include a list of potential identified test entities, as determined by the entity identifier 133. That is, such identified test entities may be provided in response to any of the various examples of the attribute analysis signals described above, or combinations thereof.
Finally with respect to the view 142, as shown, the view generator 132 may include specific reference to, or description of the change events associated with the changes 134 of the software environment 106. As may be appreciated, such change events may be correlated with, e.g., shown in conjunction with, corresponding attributes and/or affected test entities. In this way, the test engineer may easily visualize or otherwise determine a connection between the specific changes 134 that have occurred and their affect on one or more test entities of the test management system 102.
As referenced above, it may be appreciated that the system 100 of
For example, the test management system 102 may be executed using a computing device 144 that includes at least one processor 144A which is operable to read instructions from a computer readable storage media 144B, for use in implementing the test management system 102. For example, as referenced above, the computing device 144 may represent one or more server computers which are centralized with respect to a plurality of tested systems, such as the testing system 104, within a business or other organization. Of course, similar comments apply to the tested system 104 itself. In fact, the tested system 104 may be executed at least partially using resources of the computing device 144 itself, or using resources of a separate computing device on which the tested system 104 exists and is operated.
Since the computing device 144 is intended to represent one of a potential plurality of computing devices that may be used to implement the test management system 102, it may be appreciated that elements of the test management system 102 may in fact be executed using different computers. For example, data associated with the test management system 102 may be stored in whole or in part on a separate computing device from the various functional blocks illustrated in the example of
Inasmuch as various elements of the test management system 102 are described as communicating with the testing system 104, e.g., the software environment 106, it may be appreciated that such communication may occur by way of appropriate corresponding computer interfaces, which facilitate message exchange, including associated protocol and format considerations, between the test management system 102 and the testing system 104. As such, such interfaces may be considered to exist in whole or in part within a testing system 104 itself, as shown, for example, in the examples of
In
An attribute analysis signal associated with the change in the software environment may be received (204). For example, the attribute analysis signal handler 126 may receive one or more of the various attribute analysis signals described above, which reflect, describe, or otherwise present the existence of changes 134 that have occurred with respect to the software environment 106 since the time of the collecting of the various attribute sets. For example, the attribute analysis signal indicating the presence of the changes 134 may be received or otherwise determined in conjunction with errors or other exceptions that occur in conjunction with subsequent testing of the software environment 106 which occur after the changes 134. In other examples, as described, the changes 134 may be requested from, or otherwise received from, the software environment 106, e.g., at a time subsequent to an initial testing of the software environment 106 but potentially prior to a time of a subsequent testing of the software environment 106.
An attribute based view associated with an affected attribute set associated with the change may be provided, where the attribute based view identifies an affected test entity that is affected by the change (206). For example, the attribute comparator 130 and/or the entity identifier 133 may be configured to utilize the collected attributes associated with one or more testings of the software environment 106, perhaps in conjunction with information regarding the changes 134, to thereby enable the view generator 132 to output the view 142 which, as described, provides various attribute based views which allow the test engineer to directly or indirectly determine the affected test entity of the plurality of test entities. For example, as described, the attribute based view 142 may simply include a direct listing for a comparison of various attribute sets, or affected attributes thereof, so that the test engineer may easily deduce or infer affected test entities therefrom. In these or related examples, the entity identifier 133 may directly output a specific identification of an affected test entity, (e.g., the test entity 116A or 116B), perhaps in conjunction with specific identification of corresponding ones of the changes 134 which enabled identification of the affected test entity.
Thus, in the example of
During testing of the tested system 306, API's 314 may be installed locally to detect the system 306 in order to collect or otherwise determine test entity attributes 316. In other words, with reference to
At a later time which is subsequent to such testing of the tested system 306, it may occur that one or more changes occur within the tested system 306. In such cases, an API 318 to receive associated change events may be included within the test management system 304 and may communicate with a corresponding change event generator 320 installed locally to the tested system 306. In other words, such generated change events may correspond to the attribute analysis signal described above, and the API 318 and change event generator 320 may correspond in whole or in part to the change event handler 138 in the example of
Further, transaction attributes 326 may relate to virtually any transaction that may occur in association with the tested system 306. For example, a user may be tasked with executing certain financial transactions, which may include exchange of associated financial documents. In such examples, it may occur that a financial document associated with a transaction may initially be associated with, or require, a first authorization level of a user, but at a later time, may be changed to require a second, higher authorization level. In such a case, testing of the tested system 306 may provide an erroneous result, because the test entity associated with testing such transactions/documents may return a result that is allowable for a particular user to execute the specified transaction, when in fact the user may not have the newly-required authorization level needed to complete the transaction.
Switch attributes 328 may refer generally to any characteristic of the tested system 306 which may be switched (e.g., turned on or turned off) within the context of the tested system 306. For example, certain software may be associated with various versions, such as, e.g., a student version, a home user version, or a professional version. It may occur that all the versions are included with the same software, but that associated functionality is switched on or off for a particular user, or in a particular user environment. Similar attributes may exist with respect to hardware elements of the tested system 306, e.g., such as when a functionality such as Bluetooth or other optionally configured hardware functionality is enabled or disabled.
A final example of a source of change events which may be generated by the change event generator 320 is illustrated as including software components 330. As may be appreciated, such software components 330 may represent virtually any software application, object, script, or other component which may be installed within the tested system 306, and which may be subject to addition, deletion, or alteration.
Thus,
Further in the example of
Thus,
It may be appreciated that such functionality leverages, and is substantially similar to, functionality described above with respect to, e.g., the test entity 308 and test entity attributes 310-312. Consequently, further details of use of the third party test management system 332 is not provided herein. Rather, one of skill in the art would appreciate that an operator of the system 300 may benefit from being able to identify potentially affected test entities associated with changes within a software environment, even when test management functionality is provided by, or in association with, a third party provider.
In
In particular, in
As described above, such changes may not be detected until if and when an actual exception occurs and during the second or other subsequent testing. In other examples, however, it may occur that the change identifier 404 requests an indication of such changes from the API 408, without necessarily waiting for such subsequent testing to begin and/or to reach an exception stage.
If the test case in question is an initial test (506), where an initial test may refer either literally to a first test of a tested system, or to a test which is considered to be a baseline or representative example, then it may be appreciated that there will be no attribute set which may serve as a basis for comparison of either subsequent attributes, or of associated change events associated with the tested system. Consequently, the system may wait for a designated time to past, and/or until a change in the associated software environment is determined to occur (508). For example, a designated time may be set prior to execution of the operations of flowchart 500 and, additionally or alternatively, the system may be configured to retrieve or otherwise receive or determine changes in the associated software environment, as described above.
Then, the subsequent test case may be begun (502), during which grouped attributes may again be collected (504). In this case, such a subsequent test will not be an initial test (506) and the system may thus determine whether the test was successful (510).
If the test was not successful (510), then an exception may be determined and an attribute comparison may be output for comparison with a previous attribute set from the previously executed test case (512). Using such an attribute comparison, one or more related test entities may be identified (514). For example, such scenarios may correspond to the examples above with respect to
If, however, the subsequent test was successful (510), then at least one of at least two possible outcomes may result. Specifically, as shown, in one example implementation, it may be determined at some point thereafter whether a change event was received (516), e.g., from the change event generator 320 of
On the other hand, when no change event is detected or received (518, 516), then, after a period of time, it may occur that a new test case is begun (502). In this case, further execution of the operations 502-520 of the flowchart 500 may proceed.
Other embodiments and variations will be apparent to one of skill in the art. For example,
As shown, the test data 604 may include a first variant (VAR—1), and a second variant (VAR—2). Similarly, the test script 606 includes a first version (version 1), and a second version (version 2). Consequently, it may be appreciated that various combinations of the variants and versions of the test data 604 and test script 606 may be selected according to the overall test configuration 602, in order to provide desired types of testing for one or more software environments.
Further, the test script 606 may be used by itself within a test configuration 602, or may call one or more other test scripts in order to provide different or additional testing within the same or different software environments. For example, as shown in
As shown in the example of
In the example, then, three different results for the 3 different testing scenarios of the test configuration 602 may be output, and, correspondingly, 3 different collections of attributes 616, 620, 622 also may be collected. Specific, as shown, a log 618 may include for the test configuration 602 and application of version 1 of the test script 606 using variation 1 of the test data 604. Meanwhile, a log 620 may include, for a test configuration 602, and the test script in version 1 of the test script 606, and an output relying on an input of variant 2 of the test data 604. Finally, in
Thus, it may be appreciated that the test entities as discussed above with respect to
Example relationship(s) between the entities Test Configuration, Test Script/Test Script Version, Test Data Container and Test Attributes Set are explained below. For example, in a relation between Test Configuration and Test Attributes Set, there may be at most one Test Attributes Set for a Test Configuration. The mapping between Test Configuration and Test Attributes Set may be kept in a mapping table. A Test Attributes Set may be available to only one Test Configuration. If a Test Configuration is deleted, the corresponding Test Attributes Set may also be deleted. If a Test Configuration is renamed, this will have no affect on the Test Attributes Set, and instead just the corresponding mapping table may be updated (described in more detail below with respect to
In a relationship between Test Script/Test Script Version and a Test Attributes Set, when a Test Configuration is executed, it generally runs the Test Script assigned to it. The Test Script assigned to the Test Configuration can also call other Test Scripts, so a hierarchy of Test Script Calls can be the result of a Test Configuration
Execution. A Test Attributes Set will contain the attributes for all the Test Scripts called in this call sequence. Thus, one Test Attributes Set can contain data for many Test Scripts(at different hierarchy levels) for each execution of a variant in Test Configuration.
In a relationship between a Test Data Container and a Test Attributes Set, there may not be an explicit assignment therebetween. Rather the variants of a Test Data Container can be used in a Test Configuration and a Test Configuration can be executed for these variants. Since the Test Attributes Set will contain the execution specific attributes per Test Script/Test Script Version/Variant ID combination, the assignment to Test Data Container need not be explicitly saved anywhere.
With reference again to
In this regard, the execution related test attributes may be saved in Test Attributes Set database tables (see, e.g.,
Within the test attribute set 708, the example attributes 712-720 correspond generally to the various examples of software attributes already described above. Consequently, the example of
Thus, as shown in
If the creation fails (810), then the corresponding exception may be raised (812). If not (810), then the test attribute set of the corresponding test case may be locked (814). If such a lock fails (816), then a corresponding exception for a lock failure may be raised (818). If not (816), then execution specific test attributes may be created (820). If such creation does not fail (822), then the process 800 may complete. On the other hand, if creation does fail (822), then corresponding exception for execution attribute creation failure may be raised (824).
If the test attribute set does not yet exist (904), then the test attribute set may be created (912). If creation fails (914), then a corresponding exception for the creation failure may be raised (916). If the creation does not fail (914), then creation may proceed with locking of the test attribute set of the test case (918). If such lock fails (920), then the corresponding exception for the lock failure may be raised (922). If not (920), then the execution specific test attributes may be created (924). If the creation does not fail (926), then the process 900 may complete a process of creation, however, if it does fail (926), then a corresponding exception for failure of the creation of the attribute set may be raised (928).
Finally, the Test Attributes Set data may include two paths of data. The first one is the hierachical structure of the scipts called in a Test Case, and the list of systems and clients on which these scripts are called. The second path of data includes the test attributes generated for objects such as, e.g., screens, transactions, and switches, and these data are independent of the script call hierarchy, but dependent on the systems/clients for which the scripts are called.
The following includes a number of example detailed descriptions of function modules and/or methods of classes that may be used in the system 100 of
Function Group ECATT_EXTERNAL_TOOL: This function group is a placeholder for the function modules which gives the third party test tools access.
Function Module ECATT_SET_XML_INFO: Input may include an Object List for which Test Attributes must be read from Tested Systems, and Information Type(e.g., the test attributes). This function module may create a test attributes set when it is called from a third party test tool. The function module will receive a list of objects for which attributes must be generated and will call the function modules of function group AGS_SMT_TSAT_METADATA_RFC in the tested systems for reading the attributes of objects and saving them in the persistency layer.
Function Group AGS_SMT_TEST_ATTR_SET_DB: this function group may hold one Update Enabled function module for saving the Test Attributes Set data to the database tables. The other operations related to Test Attributes Set entities may be programmed in the corresponding Business Object classes for these entities as shown in the class diagram of
Function Module AGS_SMT_SAVE_TEST_ATTR_SETS_UPD_DB: Input may include Test Attributes Set header data, List of executions of a Test Configuration, a list of systems on which a test is executed, a list of user defaults data, list of user parameters, a list of switch data, a list of test script data, a list of transaction data, and a list of GUI data. This update enabled function module may be used to save the test attributes set data to the database
Function Group AGS_SMT_TSAT_METADATA_RFC may include the following function modules.
Function Module AGS_SMT_TSAT_READ_DYNPRO_DATA for reading GUI attributes from remote systems, with
Function Module AGS_SMT_TSAT_READ_SWITCH_ATTRS, which read switch attributes from remote systems, with
Function Module AGS_SMT_TSAT_READ_SW_COMPONENT, which reads the software component attributes from a remote system, with
Function Module AGS_SMT_TSAT_READ_TRNSC_DATA, which reads the transaction attributes from a remote system, with
Function Module AGS_SMT_TSAT_READ_USER_DATA, which reads the user parameters and user defaults from a remote system, with
Function Group AGS_SMT_TEST_ATTR_SET_APPL may include the following function modules.
Function Module AGS_SMT_GENERATE_TEST_ATTR_SET, which generates a test attributes set using the data in the corresponding log given as input, e.g.,
Function Module AGS_SMT_TSAT_COMPARE_TEST_ATTR, which compares the test attributes set data of two logs given for a specific test script, with
Meanwhile, Class CL_AGS_SMT_TSAT_SET is a class which includes the Business Object Layer class which represents a Test Attributes Set. The class may be a container for the Create/Update/Read/Delete methods of a Test Attributes Set and also may hold methods for checking if the test entity assigned to a Test Attributes Set is broken (or likely broken), depending on the changes in the objects for which attributes are saved as Test Attributes. The methods of this class will be as below:
Thus, this method returns an instance of the Test Attributes Set class if there is already a test attributes set for the Test Case given. If not, an empty reference is returned to the caller.
The following method returns instances of the Test Attributes Set class if there is already a test attributes set for the Test Attributes given. If not, an empty reference is returned to the caller. This method can be especially useful for the publish/push methodologies described above for detecting affected test entties. Given a list of changed test attributes, all the test attribute sets in which the changed attributes are saved can be checked, and it may be checked whether the Test Case assigned to the Test Attributes Set is broken:
The following method returns an instance of the Test Attributes Set class if there is already a test attributes set for the GUID given. If not, an empty reference is returned to the caller.
The following method returns instances of the Test Attributes Set class if there is already a test attributes set for the log id given.
The following method is a factory method for creating an instance of the Test Attributes Set and other sub-objects belonging to the Test Attributes Set
The following private constructor of the class creates an instance of the class CL_AGS_SMT_TSAT_SET
The following method compares the list of changes given with the attributes saved in a database in order to find out if the Test Case assigned to the Test Attributes Set is (already) broken.
The following method saves the changes made to the Test Attributes Set to the database.
The class CL_AGS_SMT_TSAT_SET_LOG_OBJLNR is the Business Object Layer class which represents test attributes data for a specific Test Configuration/Test Script/Version/Variant ID at a specific position of a Log. The class may be a container for the Create/Update/Read/Delete methods and comparison method(s) for the Test Configuration/Test Script/Version/Variant ID combination given, as described above.
In this class, the following method returns a list of instances of the business object layer class for a given Log ID.
The following method returns a list of business object layer classes for a given Test Case Name.
The following method returns a list of business object layer classes for a given Test Attributes Set GUID.
The following method creates an instance of the class and returns the reference to the caller.
The following private constructor creates an instance of the class:
The following method receives a reference to the business object class and compares the test attributes set data given in the reference taken with the test attributes set data of the current instance.
The following method provides a list of differences in specified test attributes.
The following method provides persistence of attribute set(s).
The class Class CL_AGS_SMT_TSAT_SET_UI_ATTR may represent the abstract Business Object Layer class which represents attributes of a User Interface Element called in a Test. This class represents all user interface elements regardless of in which technology they are programmed.
The following method returns a list of instances of the business object layer class for a given Test Case Name. All UI attributes belonging to a Test Case are represented by the list of object instances returned to the caller.
The following method returns a list of business object layer classes for a given Test Attributes Set GUID. All UI attributes may belong to a Test Attributes Set GUID.
The following method returns a list of business object layer classes for a given Log ID/Obj Lnr combination.
The following method creates an instance of the UI attribute class.
The following method creates a flag showing whether a UI attribute has been changed.
The following method shows UI field names and characteristics.
The class Class CL_AGS_SMT_TSAT_SET_DYNP_ATTR inherits from the abstract class CL_AGS_SMT_TSAT_SET_UI_ATTR and represents the attributes of a Dynpro screen.
The class Class CL_AGS_SMT_TSAT_SET_WEBDY_ATTR inherits from the abstract class CL_AGS_SMT_TSAT_SET_UI_ATTR and represents the attributes of a Web Dynpro screen.
The class Class CL_AGS_SMT_TSAT_SET_SW_ATTR represents the software component attributes of a Test Attributes Set.
In this class, the following method returns a list of instances of the business object layer class for a given Test Case Name. All Software Component attributes belonging to a Test Case are represented by the list of object instances returned to the caller.
The following method returns a list of business object layer classes for a given Test Attributes Set GUID. All Software Component attributes belonging to a Test Attributes Set GUID are returned to the user.
The following method returns a list of business object layer classes for a given Log ID/Obj Lnr combination.
The following method creates an instance of the test attributes set software component attributes class and returns it to the user.
The following private constructor creates an instance of the Software Components class.
The class Class CL_AGS_SMT_TSAT_SET_USER_ATTR is the abstract Business Object Layer class which represents attributes of a Test User.
In this class, the following method returns a list of instances of the business object layer class for a given Test Case Name. All User attributes belonging to a Test Case are represented by the list of object instances returned to the caller.
The following method returns a list of business object layer classes for a given Test Attributes Set GUID. All Test User attributes belonging to a Test Attributes Set GUID are returned to the user.
The following method returns a list of business object layer classes for a given Log ID/Obj Lnr combination.
The following method creates an instance of the test attributes set user attributes class and returns it to the user.
The following private constructor creates an instance of the Test User Attributes Class.
Implementations of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Implementations may implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. A computer program, such as the computer program(s) described above, can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.
Method steps may be performed by one or more programmable processors executing a computer program to perform functions by operating on input data and generating output. Method steps also may be performed by, and an apparatus may be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. Elements of a computer may include at least one processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer also may include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory may be supplemented by, or incorporated in special purpose logic circuitry.
To provide for interaction with a user, implementations may be implemented on a computer having a display device, e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.
Implementations may be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation, or any combination of such back-end, middleware, or front-end components. Components may be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (LAN) and a wide area network (WAN), e.g., the Internet.
While certain features of the described implementations have been illustrated as described herein, many modifications, substitutions, changes and equivalents will now occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the scope of the embodiments.
