DUCOA 05 - Remarkable Extensibility

Addition of New UI Controls [Case 01]: DUCOA Test Automation Framework offers extensibility that is really remarkable. In case new UI Controls or GUI Objects are added to the application (SUT or AUT), you may not really have to do anything about it. In the context of this Automation Framework, we are not really interested in all the UI Controls or GUI Objects of the SUT here. We are just interested in all the TYPES or Classes of unique UI Controls or GUI Objects of the SUT. And, there is a very high possibility that the new UI Controls or GUI Objects added to the SUT (Software Under Test) belong to one or more TYPE (s) Class (es) of UI Controls or GUI Objects that we have already taken care of in our Framework (Automation or Infrastructure Code).

Addition of New UI Controls [Case 02]: In case, the new UI Controls or GUI Objects added to the SUT (Software Under Test) does NOT belong to one or more TYPE (s) of UI Controls or GUI Objects that we have already taken care of in our Framework, we just need to add a few pieces of Automation Code (Function or Method) pertaining to the TYPE (s) or Class (es) of those new UI Controls or GUI Objects. In case there are changes to a few UI Controls or GUI Objects, we may not have to change the Automation Code (Function or Method) pertaining to the TYPE (s) or Class (es) of those UI Controls or GUI Objects in question. Those changes could be absorbed in the UI Controls repository.

Replacement of UI Controls: In case some of the UI Controls or GUI Objects are replaced with a new set of UI Controls or GUI Objects and the new set of UI Controls or GUI Objects do not belong to the TYPES or Classes already taken care of in the Framework, we just need to add a few pieces of Automation Code (Function or Method) pertaining to the TYPE (s) or Class (es) of those new UI Controls or GUI Objects. And, in this case, we do not have to throw away any method or function pertaining to the UI Controls or GUI Objects that are gone. For, the Methods and Classes are for the Types or Classes of UI Controls; and not for individual instances of those UI Controls.

Change in Functionality of SUT: In case of a Functionality Change in the SUT, a workflow may involve a different sequence of instances of interaction (than the original one) with UI Controls or GUI Objects. In that case, required changes are made in the Translated and Composed Tests. And, that's the only set of changes that need to be done. It does not require a change in the code.

Changes to UI Controls: In any case, if there are changes to the UI Controls or GUI Objects that are associated with tests that have already been automated, the related Translated and Composed Tests may not be changed. For, the changes may be absorbed in the UI Controls repository. And, again, the Automation Code (Functions or Methods) underneath , only pertaining to the TYPE or Class of the UI Controls or GUI Objects that have been changed, is modified, only if required, to make that capable of performing the intended operations or verifications on the TYPE or Class of the UI Controls or GUI Objects that have been changed.

Automation of New Tests: In case new tests are created and lined up for automation, it just takes creating new Translated and Composed Tests and adding new entries in the Test Driver File (Test Set).  Next Page >>

Creative Commons License
DUCOA 05 - Remarkable Extensibility by Debi Prasad Mahapatra is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License.

Comments

Popular Posts