This session looks at common issues with just relying on end to end automation testing tools, using examples to demonstrate common pitfalls and how visual testing can help add another tool to your tool belt.
The talk looks at why we automate tests, the issue with just manually testing, common end to end automation pitfalls, a brief introduction to visual testing and finally a look at common issues with visual testing and ways to overcome them.
Through the use of interactive examples the audience will gain an understanding of why relying on just manual testing can become an issue and how too much automation has a negative impact by looking at testing anti-patterns. The audience will also learn what visual testing is, what tools are available, some of the common pitfalls of using visual testings as well as tips on ways to overcome them based on experience of creating a custom visual test framework at my current employer.
3. @11vlr
• Previously a Software Engineer for
7 years (.Net C#)
• Currently a Senior Test Engineer
@Vizolution
• Code Club volunteer
• Organiser of SwanseaCon
• Co-organiser of DDD Wales
ABOUT ME
4. • Automated testing is more reliable, as
it is performed by tools and/or scripts.
• Automated testing is executed by
software tools, so it is significantly
faster than a manual approach.
WHY AUTOMATE END
TO END UI TESTS?
@11vlr
5. @11vlr
• Investment is required
• Automated testing is a practical option
when the test cases are run
repeatedly over a long time period.
• Automated testing entail
human observation and cannot
guarantee user-friendliness or positive
customer experience.
COMMON UI
AUTOMATION ISSUES
DOES NOT
12. @11vlr
WHY NOT JUST STICK
WITH MANUAL
TESTING THEN?
• Manual testing allows for human
observation, which may be more
useful if the goal is user-friendliness
or improved customer experience.
UI
Service
Unit
Manual &
Exploratory
Testing
13. @11vlr
• Can be time intensive
• Is not accurate at all times due to
human error, hence it is less reliable.
• Is time-consuming, taking up human
resources.
• Is only practical when the test cases
are run once or twice, and frequent
repetition is not required.
MANUAL TESTING
17. @11vlr
• Open source; anybody can see the
code and help
• Big community of support
• Can operate on almost any OS
• Multiple language support (Python,
Ruby, .Net, PHP, Java, JavaScript)
• Supports a range of browsers like
Opera, Chrome, IE (6,7,8,9,10,11),
Mozilla Firefox, Safari
SELENIUM
37. @11vlr
• Didn’t work straight out of the box
and/or contained lots of bloat
• Steep learning curve
• Small community so lack of support
• Needed to work with our current
automation framework
• Costs
ISSUES WITH OTHER
OFFERINGS
38. @11vlr
• Still in development
• Facing many challenges which are
because of the products we offer, the
ways in which we have developed
them and the way in which we test
them
ROLLING OUR OWN