This document discusses automation testing and provides tips for getting started with test automation. It recommends starting with end-to-end smoke tests using an easy language and tools. Specific suggestions include using C# with the nSelene library or Java with Selenide. The document emphasizes that automation is a tool to help testers do their work more efficiently, and that one can start automating even without manual testing experience if they have support and learn the basics.

1. Easy Automation
C# version

2. Preface…

3. Why Automation?

4. Testing
=
Assessing Quality

5. Effective Testing
=>
Assessing Quality
0
50
100
150
200

6. Automation
=
Automating manual routine work

7. Effective Testing
*=
Testing with automated routine
work

8. Automation!

9. But, it’s hard, no?

10. No:p

11. Coding Session

12. Summary

13. Coverage Styles
End to End style
+ more coverage in
less time with less
efforts during
implementation
+ integration coverage
Unit/One-feature-per-test
style
+ in case of bugs, gives
more complete report
+ easier to identify reason
from the report
=>
+ less time and efforts in
support

14. How many => => Only:
+ functional
high priority
use cases

15. Avoid => => No
- style checks
- low priority test cases
(that user will not do
on regular basis)
- additional requirements,
like “different kind of names
for entities”
<=

16. Implementing Automation
• Project in progress, no Automation?
1. start with End To End style smoke integration
tests
2. review and test plan
3. cover with “One feature”/“Unit” style
independent tests

17. Implementing Automation
• Project just started OR ready features are
automated?
1. Test plan new features
2. Cover with “One feature”/“Unit” style
independent tests
3. Add End to End integration smoke tests

18. Wasn’t it Easy? :)

19. How to start?
• Choose language
• Learn language (books, interactive tutorials,
koans, exercism.io, etc.)
• Choose Easy Tools
• Find a mentor (friend, dev on your project, chat,
etc…)
• Go :)

20. Choose language?
• Have project?
• choose language of project’s developers
• Have no project but want to find work fast?
• choose one of the most popular language
• Have no project but want to code in your style, and it
does not matter how long will you seek for the job?
• choose language that fits you

21. Learn language?
Google :p

22. koans + docs.seleniumhq.org + google.com
=
“You can do this in any language.”

23. Easy Tools?
• Just a few examples…
• C#: nSelene (or jSelenide via JNI)
• Java: Selenide
• Ruby: Capybara + SitePrism
• Python: Selene

24. No Tool for your language?
• Have project?
• ask project’s developers to write it for you
• Have no project and lack of knowledge?
• switch to language that has easy tools :)
• Brave?
• implement it by your own ;)

25. Can I start with no manual
experience?
Automation is just a tool, which can be pretty easy, as you saw:),
so:
• IF
• you are smart and brave
• have guys who will help you
• know where to find “easy automation tricks&tools”
• THEN
• why not? :)

26. Just Remember…
• Automation is NOT a separate Role
• Automation IS A TOOL for Test Engineer to do his
work effectively

27. Q&A

28. github.com/yashaka
github.com/yashaka/nselene
yashaka@gmail.com
@yashaka
Thank You