Anti pattern of using Robot framework

1. RUIN YOUR LIFE using ROBOT FRAMEWORK
Prayoch Rujira
ROBOT FRAMEWORK MEETUP #1 2017

2. Not right of wrong.
Just consequences.

3. No ATDD applied

5. Without ATDD
• Bad relationship in product team
• unreliable test cases
• No shared understanding
• No actual progress
• Bad software design

8. No source control

9. Without source control
• No versioning
• No permanent storage
• Risk losing code

10. Try git
https://try.github.io/

11. No Continuous
Integration

12. Without CI
• No automatic regression test runner
• Late/Slow feedback

15. Less maintenance

17. Without rapid maintenance
• Invite broken windows
• Hard to change

18. Undescriptive
naming

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 )

28. Dependencies
between test cases

30. With dependencies between
tests
• Hard to maintain
• Hard to fix problem in specific cases

35. Multiple assertions

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

41. from https://watirmelon.com/2012/01/31/introducing-the-software-testing-ice-cream-cone/

42. from https://watirmelon.com/2012/01/31/introducing-the-software-testing-ice-cream-cone/

43. Testing visual
elements

44. Examples
• Alignment
• Color
• CSS Attribute
• And more…

45. With testing visual elements
• Extremely invite fragile test
• Increase unnecessary development cost

46. from https://enna.com/2015/08/11/robots-coming-future-autonomation/
Jidohka

47. UX

48. Behaviour and
behaviour only

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

58. Bad error message

61. With bad error messages
• Extremely hard to fix problem

63. The worst

64. No automated test
at all

65. The Boomerang Jobs

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. ของฝากนักกอลฟ์

74. Respect abstraction level

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

77. Robot framework user
guide
http://robotframework.org/robotframework/latest/
RobotFrameworkUserGuide.html

79. อันนี้ห้ามลืม
somkiat.cc

80. Questions?

81. Feedback please.