Ruin your life using robot framework
- 1. RUIN YOUR LIFE using ROBOT FRAMEWORK Prayoch Rujira ROBOT FRAMEWORK MEETUP #1 2017
- 2. Not right of wrong. Just consequences.
- 5. Without ATDD • Bad relationship in product team • unreliable test cases • No shared understanding • No actual progress • Bad software design
- 9. Without source control • No versioning • No permanent storage • Risk losing code
- 12. Without CI • No automatic regression test runner • Late/Slow feedback
- 15. Less maintenance
- 17. Without rapid maintenance • Invite broken windows • Hard to change
- 20. Without descriptive naming • Hard to maintain codebase • Hard to find bugs • Hard to understand
- 21. Naming • Very important to 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 as steps
- 24. With test cases as steps • Invite duplication • No reusable
- 27. Good test case consist of • Arrange ( Given ) • Action ( When ) • Assert ( Then )
- 30. With dependencies between tests • Hard to maintain • Hard to fix problem in specific cases
- 37. With multiple assertions • Invite fragile test • Hard to maintain • Hard to fix problem in specific cases
- 38. Overuse
- 40. With overusing • Increase test execution time • Increase maintenance cost • Invite fragile test
- 44. Examples • Alignment • Color • CSS Attribute • And more…
- 45. With testing visual elements • Extremely invite fragile test • Increase unnecessary development cost
- 47. UX
- 49. No or less using tags
- 50. Without tags • May block development process • Slow down feedback loop • Hard to manage
- 53. Tags example • Story ID • External systems • Sprint number • Critical level • Feature name • Module name • Version • Profile
- 54. Hacking
- 57. With hacked tests • Unreliable tests • Real problem still exist • Lead to disasters
- 61. With bad error messages • Extremely hard to fix problem
- 63. The worst
- 64. No automated test at all
- 66. Without automated test • Summon boomerang jobs • Regression test over and over again • War room
- 68. Recap
- 69. • Start with ATDD • Use source control ( GIT Recommended ) • Use CI • Fix problems as soon as possible
- 70. • Naming with care • Respect tests as a source code • Merciless refactoring • Write the test you want to read
- 71. • Focus on behaviour • Separate human jobs from computer jobs • Manage with tags • One better than none!
- 72. ของฝากนักกอลฟ์
- 75. Slide: Robot framework dos and don’t http://www.slideshare.net/pekkaklarck/robot-framework-dos- and-donts
- 76. How to write good test cases using Robot Framework https://github.com/robotframework/ HowToWriteGoodTestCases/blob/master/ HowToWriteGoodTestCases.rst
- 80. Questions?
- 81. Feedback please.