Download - Clarice Technologies - Agile QA
Shaping Ideas intoExemplary User Experience
ClariceTechnologies
“We are a Product Development Company, specializing in UX Design and Web/Mobile Development”
3
Agile UI
by Mukesh AgarwalTechnical LeadClarice Technologies
Clarice Technologies
4Clarice Technologies
Who Moved My Label?
5Clarice Technologies
Who Moved My Label?
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 the issue by taking below points into consideration:
• Preventive Measures
• Curative Measures
6Clarice Technologies
Preventive Measures
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 test cases / automation scripts based purely on 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.
7Clarice Technologies
Preventive Measures
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 thus contribute towards Design QA.
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.
8Clarice Technologies
Preventive Measures
Below is a basic flow diagram which will help you visualize this problem better followed by certain ideas to solve the problem mentioned above:
9Clarice Technologies
Curative Measures
Fix a Time bound Milestone to Update Test Cases
At the test plan level incorporate some buffer and plan bandwidth to update the test cases based upon any design change that may come 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.
10Clarice Technologies
Curative Measures
Build Milestone
When projects have frequently changing designs/functionality, we need to focus on and check the features which are getting implemented/updated in the upcoming build. We 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.
11Clarice Technologies
Curative Measures
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 design much ahead of the actual change. In the mean time we could think of a QA strategy and plan for anticipated design change.
Thank You
For More Information : www.claricetechnologies.com
Pune | Bangalore | USA
Thank Youwww.claricetechnologies.com
Pune
1st fl, Pride Purple AccordOpposite Symantec buildingBaner Road, Pune 411045
Phone: +91 (20) 4078 9520
Bangalore
1st fl 651, 13th Cross, 27th Main, HSR Layout, Sector 1, Bangalore 560095
Phone: +91 (80) 4161 7136
USA
19925 Stevens Creek Blvd.Suite 100, Cupertino,CA 95014-2358, USA
Phone: +1 (650) 646 2553