Agile Testing Methodology
In Agile projects, teams come together to design, develop and test functionality. As the team developing and testing the code are the same, they often take a behavior driven development approach. This means that they put their users at the centre of everything that they do, so when they develop functionality, they test it based on the behavior that the user expects.
In addition, quality is really important in agile teams. As they develop concepts into production ready systems it is vital that teams ensure quality at all stages. To achieve this, teams focus on preventing, rapidly identifying and fixing user and business focused bugs.
Behaviour Driven Development Definition
This means that they put their users at the centre of everything that they do, so when they develop functionality, they test it based on the behavior that the user expects.
Test Driven Development Definition
Teams that work in a Test-Driven Development manner first write Unit Tests for how the functionality should work, then produce functional code to pass those tests. Teams can analyse their code using tools (such as SonarQube) and make ammendments accordingly.
Difference between User Experience and User Interface Design
The User Interface (UI) is an extremely important part of the design. It is essentially what the user interacts with. However, it is important that the UI and UX work well together. Despite their professional relationship, the roles themselves are quite different. UX Design is a more analytical and technical field, UI Design is closer to what we refer to as graphic design.
The designer and expert Helga Moreno puts it quite simply in her article The Gap Between UX And UI Design: “Something that looks great but is difficult to use is exemplary of great UI and poor UX. While Something very usable that looks terrible is exemplary of great UX and poor UI.”
What are the Agile Testing Quadrants?
User interface testing is the technique used to identify where there are defects in a product or software. This process is called Graphical User Interface [GUI] Testing.
There are three main approaches to GUI Testing:
- Manual Based – Based on the domain and application knowledge of the tester.
- Capture and Replay – Based on capture and replay of user actions.
- Model-based testing – Based on the execution of user sessions based on a GUI model. This can be in the form of an event-based model, a state-based model or a domain model.
Here is a checklist for when you want to test the User Interface of a screen:
- Check Screen Validations
- Verify All Navigations
- Check usability Conditions
- Verify Data Integrity
- Verify the object states
- Verify the date Field and Numeric Field Formats
Agile Testing Strategy
The online training website Treehouse states that there are 10 main UI principles. They are:
- Know your user
- Pay attention to patterns
- Stay consistent
- Use visual hierarchy
- Provide feedback
- Be forgiving
- Empower your user
- Speak their language
- Keep it simple
- Keep moving forward
This seems like a pretty good starting point. For more information, go to their article “10 user interface design fundamentals”.
Agile Testing Days Conference
The Agile Testing Days Conference is a festival for the agile community. It is a chance to network & get deep insights in testing & agile excellence. The conference covers a number of topics, including:
- State of the Art Testing
- Leadership in Agile
- Scrum Exellence
- Techniques & Metrics
- IT Project Management
- Test Automation
- Mobile & IoT
- Agile Testing & QA
- Personal Improvement
All imagery has been created by and is Copyright of Samuel Fry. Vector image credit to “Stylized London Vectors” by OffsetMedia.co.uk, “Variety of cartoon buildings” by Freepik.com,“Buckingham palace London monuments vector” by Free Vector, “Man working on his computer” by Freepik.com and “Avatar People” by Freepik.com. All Creative Commons.