Download as PDF, PPTX
More Related Content
Similar to Ruin your life using robot framework
Ruin your life using robot framework
- 1. RUIN YOUR LIFEusing ROBOT FRAMEWORK Prayoch Rujira ROBOT FRAMEWORK MEETUP #1 2017
- 2. Not right ofwrong. Just consequences.
- 3.
- 5. Without ATDD • Badrelationship in product team • unreliable test cases • No shared understanding • No actual progress • Bad software design
- 8.
- 9. Without source control •No versioning • No permanent storage • Risk losing code
- 10.
- 11.
- 12. Without CI • Noautomatic regression test runner • Late/Slow feedback
- 15.
- 17. Without rapid maintenance •Invite broken windows • Hard to change
- 18.
- 20. Without descriptive naming •Hard to maintain codebase • Hard to find bugs • Hard to understand
- 21. Naming • Very importantto name well test cases, test suites, keywords, variables, libraries, resource files, … • Consistency • Namespaces • Name should tell “What” not “How” from slide http://www.slideshare.net/pekkaklarck/robot-framework-dos-and-donts
- 22. Test cases assteps
- 24. With test casesas steps • Invite duplication • No reusable
- 27. Good test caseconsist of • Arrange ( Given ) • Action ( When ) • Assert ( Then )
- 28.
- 30. With dependencies between tests •Hard to maintain • Hard to fix problem in specific cases
- 35.
- 37. With multiple assertions •Invite fragile test • Hard to maintain • Hard to fix problem in specific cases
- 38.
- 40. With overusing • Increasetest execution time • Increase maintenance cost • Invite fragile test
- 41.
- 42.
- 43.
- 44. Examples • Alignment • Color •CSS Attribute • And more…
- 45. With testing visualelements • Extremely invite fragile test • Increase unnecessary development cost
- 46.
- 47.
- 48.
- 49. No or lessusing tags
- 50. Without tags • Mayblock development process • Slow down feedback loop • Hard to manage
- 53. Tags example • StoryID • External systems • Sprint number • Critical level • Feature name • Module name • Version • Profile
- 54.
- 57. With hacked tests •Unreliable tests • Real problem still exist • Lead to disasters
- 58.
- 61. With bad errormessages • Extremely hard to fix problem
- 63.
- 64.
- 65.
- 66. Without automated test •Summon boomerang jobs • Regression test over and over again • War room
- 68.
- 69. • Start withATDD • Use source control ( GIT Recommended ) • Use CI • Fix problems as soon as possible
- 70. • Naming withcare • Respect tests as a source code • Merciless refactoring • Write the test you want to read
- 71. • Focus onbehaviour • Separate human jobs from computer jobs • Manage with tags • One better than none!
- 72.
- 74.
- 75. Slide: Robot framework dosand don’t http://www.slideshare.net/pekkaklarck/robot-framework-dos- and-donts
- 76. How to writegood test cases using Robot Framework https://github.com/robotframework/ HowToWriteGoodTestCases/blob/master/ HowToWriteGoodTestCases.rst
- 77.
- 79.
- 80.
- 81.