In-Sprint Automation - An Automation approach in Agile Environment.

-
In-Sprint Automation In Agile - 

 In-Sprint Automation - In Sprint automation is process to start automation early in Sprint & complete it with in Sprint. Most of project now a days followed Agile framework, Sprints start with Story selection & development of stories. In traditional automation approach Test Team needs to wait till Stories delivered i.e. UI is ready or Web Services are deployed. Stories normally delivered mid of Sprint of towards end of sprint so automation could not be started or completed within Sprint.
In-Sprint Automation handle this problem by Starting Automation activities when Sprint starts so automation could be completed within Sprint.

In-Sprint Automation Preconditions-
To Start In-Sprint automation Test Engineers must be involved in all agile activities i.e. they should be involved in Product Grooming , Story Pointing, Backlog Grooming etc. so they had complete knowledge of the product & all new functionalities.
For UI automation Test Engineers should know all XPaths & functions to be used on pages. These XPaths should be provided by development team or they should inform Id's, Name's , LinkTexts or other identifiers.
UX team should deliver wire-frames for UI designs so Test Team could take CSS elements like Color, Height, Padding etc & create XPaths. For Web Services API automation , Product Owner or Technical Architect should provide BaseURL , Resources, PostBody , Headers & Response so Test team could create base test cases.
QA Environment or UAT env or Staging should be ready.

In-Sprint Automation Process -
For UI automation Test Team requires Xpaths to identify elements, Team Team could not create XPaths unless required HTML are provided or UI is deployed. In traditional Test approach Test Team waits for UI to be up & running.
In Agile process Test Team discuss all identifiers required with Dev team, Dev team knows what they are going to develop so UI developers can provide XPaths or based on wireframes provided by UX team they can provide information for XPaths or identifiers to Test Team so test team can start writing required functions.

UX team provides wireframes to UI developers for building new pages. These wireframes have information for all major CSS elements like Height, Length, Color , Background color, Padding etc. If Test team need to validate CSS elements they need these CSS elements. So for In-Sprint automation Team Team should have wireframes handy when sprint starts so they could inspect these wire frames & start writing UI validation test cases.

For Webservices automation Test Team requires information for new endpoints , resources , headers , body & response. All of this information should be available to Test Team for creating automation test cases.
Test data for different iterations should be available or Test Team needs to generate this. When all this information is available Test team can use these information for creating new test cases. If response is available Test Team can validate response against test data


In-Sprint Automation Challenges -
Most of the time Test Team does not get XPaths / HTML files / UX designs on time so Test could not be started.
Change in Sprint Scope or requirement impacts on test automation.
Change in UI designs or functionalities resultants in more rework.
Change in CSS elements or DOM results in rework for XPaths.

Popular posts from this blog

ISTQB Mocktest 1

-
1. ___________ Testing will be performed by the people at client own locations (1M) A. Alpha testing B. Field testing C. Performance testing D. System testing 2. System testing should investigate (2M) A. Non-functional requirements only not Functional requirements B. Functional requirements only not non-functional requirements C. Non-functional requirements and Functional requirements D. Non-functional requirements or Functional requirements 3. Which is the non-functional testing (1M) A. Performance testing B. Unit testing C. Regression testing D. Sanity testing 4. Who is responsible for document all the issues, problems and open point that were identified during the review meeting (2M) A. Moderator B. Scribe C. Reviewers D. Author 5. What is the main purpose of Informal review (2M) A. Inexpensive way to get some benefit B. Find defects C. Learning, gaining understanding, effect finding D. Discuss, make decisions, solve technical problems 6. Purpo...
Read more

Cloud Byte 2 - Common AWS Services for Cloud Practitioner Certification (CCP)

-
CloudWatch - Focuses on the activity of AWS services and resources, reporting on their health and performance. You can collect & track metrics . You can use Amazon CloudWatch Logs to monitor, store, and access your log files from Amazon Elastic Compute Cloud (Amazon EC2) instances, AWS CloudTrail, Route 53, and other sources. CloudWatch Logs enables you to centralize the logs from all of your systems, applications, and AWS services that you use, in a single, highly scalable service. You can then easily view them, search them for specific error codes or patterns, filter them based on specific fields, or archive them securely for future analysis. By default, logs are kept indefinitely and never expire. You can adjust the retention policy for each log group, keeping the indefinite retention, or choosing a retention periods between 10 years and one day. CloudTrails – Who is doing what in AWS . It is a log of all actions that have taken place inside your AWS environment. AWS Cloud...
Read more

Equivalence Class Partitioning

-
ECP is a testcase design techniques that divides the input data into set of partitions of data from which test case can be derived. The thumb rule is that there should be at least one class for each of partitions. It is expected that each member of class will have same behavior in the system. In other way ECP method creates same set of Input/Output that are handled in the same way by the application. This method helps to reduce number of test cases as we create classes for of test data & test them accordingly. The test that results from the representative value for a class is said to be "equivalent" to the other values in the same class. If no errors were found in the test of the representative value, it is reasoned that all the other "equivalent" values wouldn't identify any errors either.   For ex. lets have a systesm which takes 2 integer value & add them.As we know that sum of two integer will always be a positive Integer so if we have to test w...
Read more