Clarice Technologies - Agile QA

588 views
534 views

Published on

This article discusses Agile UI and some common problems that a tester always experiences in his/her profession such as:
- How to deal with frequently changing design scenarios?
- What to do with the old test cases which are less relevant every new cycle?
- How can we reduce our re-work and still provide quality?
There isn’t a silver bullet for this and the solutions are always subjective. Solutions vary from project-to-project, however we can always minimize the intensity of the issue by taking below points into consideration:
- Preventive Measures
- Curative Measures

Clarice Technologies
www.claricetechnologies.com
Specialists in User Experience Design and Web/Mobile technologies.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
588
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
4
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Clarice Technologies - Agile QA

  1. 1. Shaping Ideas intoExemplary User Experience
  2. 2. “We are a Product Development Company, specializing in UX Design and Web/Mobile Development”ClariceTechnologies
  3. 3. Agile UIbyMukesh AgarwalTechnical LeadClarice Technologies3ClariceTechnologies
  4. 4. Who Moved MyLabel?4ClariceTechnologies
  5. 5. Well, there isn’t a silver bullet for this and the solutions are always subjective. Solutions vary from project-to-project, however we can always minimize the intensity of theWho Moved My issue by taking below points into consideration:Label? • Preventive Measures • Curative Measures5ClariceTechnologies
  6. 6. Functionality is the Key; Not UI While creating the test cases document in an environment where the design change is very frequent, it makes most sense to write testPreventive cases / automation scripts based purely onMeasures functionality. Lesser emphasis on UI elements will help reduce the rework effort and specially when majority design changes in your project are based on the UI (not work flow). Even if some design changes occur related to functionality, we can always update the test cases.6ClariceTechnologies
  7. 7. QA in Early Phase of the Cycle If we could make it a process where QA is included right at the design level, we could get rid of most of the design flaws. QA can thusPreventive contribute towards Design QA.Measures Fix the Labels Whenever we have automation involved, the labels of all UI elements such as buttons and fields should be properly maintained. So if any structural changes occur in future we don’t have to update the scripts.7ClariceTechnologies
  8. 8. Below is a basic flow diagram which will help you visualize this problem better followed by certain ideas to solve the problem mentioned above:PreventiveMeasures8ClariceTechnologies
  9. 9. Fix a Time bound Milestone to Update Test Cases At the test plan level incorporate some buffer and plan bandwidth to update the test casesCurative based upon any design change that may comeMeasures up. One should update the test cases based on the duration assigned in the test plan. This will eliminate the multiple efforts of updating test plans.9ClariceTechnologies
  10. 10. Build Milestone When projects have frequently changing designs/functionality, we need to focus on and check the features which are gettingCurative implemented/updated in the upcoming build. WeMeasures should update at least those parts of the test cases which are related to the implemented/updated features. Instead of putting off the task of updating the test case document when the design has been frozen, we should keep it updated as per changes in each build. This will gradually eliminate the huge task of updating the entire test case document at the end of the cycle.10ClariceTechnologies
  11. 11. Frequent Review with Clients/Designers As a QA, we should have frequent review of our test cases with designers and developers. We can get hold of their plan to change the designCurative much ahead of the actual change. In the meanMeasures time we could think of a QA strategy and plan for anticipated design change.11ClariceTechnologies
  12. 12. Thank YouFor More Information :www.claricetechnologies.comPune | Bangalore | USA
  13. 13. Thank Youwww.claricetechnologies.com Pune Bangalore USA 1st fl, Pride Purple Accord 1st fl 651, 13th Cross, 27th 19925 Stevens Creek Blvd. Opposite Symantec building Main, HSR Layout, Sector 1, Suite 100, Cupertino, Baner Road, Pune 411045 Bangalore 560095 CA 95014-2358, USA Phone: +91 (20) 4078 9520 Phone: +91 (80) 4161 7136 Phone: +1 (650) 646 2553

×