The document discusses strategies for implementing and testing automation in a web UI project, emphasizing high-priority use cases and functional testing. It provides a detailed outline of various actions, scenarios, and transitions needed for effective test coverage while suggesting tools and languages for automation. The author encourages starting with foundational skills and gradually progressing to more complex testing frameworks to improve efficiency and accuracy in software development.

1. You don’t need
Automation Engineer!
@yashaka

2. Automation is hard, isn’t it?

3. It isn’t:p

4. It isn’t:p
(at least WEB UI)

5. if you know how to “cook” it ;)
It isn’t:p

6. But no rush:)

7. Let’s start
from beginning…

8. Product

10. Use cases (draft)
Tree
shleep
eat
run
hang
Holes
shleep
eat
run
During All activities:
sh-shispering
Special Cases:
GIVEN shleeping
WHEN 2 meters to somebody
THEN become invisible
Transitions:
tree > holes
tree < holes

11. Choosing high priority functionality
Tree
shleep *
eat *
run *
hang *
Holes
shleep *
eat *
run *
During All activities:
sh-shispering
Special Cases: *
GIVEN shleeping
WHEN 2 meters to somebody
THEN become invisible
Transitions:
tree > holes *
tree < holes *

12. To implement first & fast
Tree
shleep *
eat *
run *
hang *
Holes
shleep *
eat *
run *
Transitions:
tree > holes *
tree < holes *

13. Scenario (End to End)
go to hole
run
go to tree
hang
eat
go to hole
shleep

14. Tracking coverage
Tree
shleep
eat e
run
hang e
Holes
shleep e
eat
run e
During All activities:
sh-shispering
Special Cases:
GIVEN shleeping
WHEN 2 meters to somebody
THEN become invisible
Transitions:
holes > tree e
holes < tree e

15. A bit messy?

16. be DRY ;)
Improve visibility

17. ActionsContext Holes Tree sh-shispering?
run !!e ! !
hang - !!e !
eat !! !!e !
shleep !!e !! !
- shleep invisible ? !! !
Transitions:
holes > trees e
holes < trees e

18. ActionsContext Holes Tree sh-shispering?
run !!e ! !
hang - !!e !
eat !! !!e !
shleep !!e !! !
- shleep invisible ? !! !
Transitions:
holes > trees e
holes < trees e
hole in coverage

19. E2E
go to hole
run
go to tree
hang
eat
go to hole
shleep
1-Feature test
go to tree
shleep invisible
Finalise smoke coverage

20. E2E
go to hole
run
go to tree
hang
eat
go to hole
shleep
1-Feature test
go to tree
shleep invisible
assert shispering
Use possibilities to improve coverage

21. ActionsContext Holes Tree sh-shispering?
run !!e ! !
hang - !!e !
eat !! !!e !
shleep !!e !! !
- shleep invisible ? !!f !f
Transitions:
holes > trees e
holes < trees e

22. Done with Smoke? - Proceed to Full Acceptance with FT
ActionsContext Holes Tree sh-shispering?
run !!e !f !f
hang - !!e !e
eat !!f !!e !f
shleep !!e !!f !f
- shleep invisible ? !!f !f

23. Coverage tips: Yes
Functional Use Cases
High priority,
(user will definitely do on regular basis)

24. Coverage tips: No
low-priority checks
“different values” checks

25. ActionsContext Holes Tree sh-shispering?
run !!e ! !
hang - !!e !
eat !! !!e !
shleep !!e !! !
- shleep invisible ? !!e !
Transitions:
holes > trees e
holes < trees e

26. No low-priority checks
ActionsContext Holes Tree sh-shispering?
run !!e ! !
hang - !!e !
eat !! !!e !
shleep !!e !! !
- shleep invisible ? !!e !

27. ActionsContext Holes Tree sh-shispering?
run !!e ! !
- fast
- slow
? ?
hang - !!e !
- low
- high
? ?
eat !! !!e !
- much
- a bit
? ?
shleep !!e !! !
- shleep invisible ? !!e !
No “different values” checks

28. ActionsContext Holes Tree sh-shispering?
run !!e ! !
- fast
- slow
hang - !!e !
- low
- high
eat !! !!e !
- much
- a bit
shleep !!e !! !
- shleep invisible ? !!e !
No “different values” checks
different variations
of same “function”

29. Should be covered
on “unit testing” level
different variations
of same “function”
- fast
- slow
- low
- high
- much
- a bit
(giving the same
“user flow”)

30. We are here => => Only:
functional
high priority
use cases
different variations
of same “function”
Here =>

31. Avoid =>
move
additional requirements,
like “different kind of names
for entities”,
“function variations”, etc…
<= to
=> from

32. Where is code ?

33. Keep calm:)

34. From

35. To

36. Actions
run, hang, eat, sleep
create, edit, delete, toggle,
toggle all
Contexts
holes, trees
fitlers:
all, active, completed

37. The same ;)

38. go to hole
run
go to tree
hang
eat
go to hole
shleep
Scenario (End to End)

39. Scenario (End to End)
given at todomvc
add "a"
toggle "a"
filter active
filter completed
edit "a" to "a edited"
toggle "a edited"
…

40. Add expected results
given at todomvc
add "a"
toggle "a"
filter active
assert no tasks
filter completed
edit "a" to "a edited"
toggle "a edited"
assert no tasks
…

41. Implicit checks are ok in “nearest steps”
given at todomvc
add "a"
toggle "a"
filter active
assert no tasks
filter completed
edit "a" to "a edited"
toggle "a edited"
assert no tasks
…

42. Demo

43. Let’s start coding ;)
given at todomvc
add "a"
toggle "a"
filter active
assert no tasks
filter completed
edit "a" to "a edited"
toggle "a edited"
assert no tasks
…

44. Help computer to read it in Java
givenAtTodoMVC();
add("a");
toggle("a");
filterActive();
assertNoTasks();
filterCompleted();
edit("a", "a edited");
toggle("a edited");
assertNoTasks();
//…

45. public class TodoMVCTest {
@Test
public void testTasksLifeCycle(){
givenAtTodoMVC();
add("a");
toggle("a");
filterActive();
assertNoTasks();
filterCompleted();
edit("a", "a edited");
toggle("a edited");
assertNoTasks();
//...
}
}

46. public class TodoMVCTest {
@Test
public void testTasksLifeCycle(){
givenAtTodoMVC();
add("a");
toggle("a");
filterActive();
assertNoTasks();
filterCompleted();
edit("a", "a edited");
toggle("a edited");
assertNoTasks();
//...
}
}
?

47. public static void givenAtTodoMVC(){
open("https://todomvc4tasj.herokuapp.com/");
newTask.shouldBe(enabled);
}
givenAtTodoMVC();

48. public static SelenideElement newTask = $("#new-todo");
newTask
CSS Selector

49. CSS Selector ?

55. [id=“new-todo"] = #new-todo

56. public static SelenideElement newTask = $("#new-todo");
newTask
[id=“new-todo"] <=> #new-todo

57. public static void add(String taskText) {
newTask.setValue(taskText).pressEnter();
}
add("a");

58. public static void toggle(String taskText) {
tasks.findBy(exactText(taskText)).$(".toggle").click();
}
toggle("a");

59. public static void toggle(String taskText) {
tasks.findBy(exactText(taskText)).$(".toggle").click();
}
toggle("a");

60. public static ElementsCollection tasks = $$("#todo-list>li");
tasks

61. public static ElementsCollection tasks = $$("#todo-list>li");
tasks

63. public static void toggle(String taskText) {
tasks.findBy(exactText(taskText)).$(".toggle").click();
}
toggle("a");

65. public static void filterActive(){
$(By.linkText("Active")).click();
}
filterActive();

66. By.linkText("Active")

67. public static void assertNoTasks() {
tasks.filterBy(visible).shouldBe(empty);
}
assertNoTasks();

68. tasks.filterBy(visible).shouldBe(empty);

69. public class TodoMVCTest {
@Test
public void testTasksLifeCycle(){
givenAtTodoMVC();
add("a");
toggle("a");
filterActive();
assertNoTasks();
filterCompleted();
edit("a", "a edited");
toggle("a edited");
assertNoTasks();
//...
}
}

70. open("https://todomvc4tasj.herokuapp.com/");
newTask.shouldBe(enabled);
newTask = $("#new-todo");
tasks = $$("#todo-list>li");
newTask.setValue("a").pressEnter();
tasks.findBy(exactText("a")).$(".toggle").click();
$(By.linkText("Active")).click();
tasks.filterBy(visible).shouldBe(empty);

71. Easy?

72. End to End
go to hole
run
go to tree
hang
eat
go to hole
shleep
Unit/1-feature-per-test
go to tree
shleep invisible
Coverage Style

73. End to End Unit/1-feature-per-test
Coverage Style
public void testFiltering(){
givenAtTodoMVC();
add("a");
toggle("a");
filterActive();
assertNoTasks();
filterCompleted();
edit("a", "a edited");
toggle("a edited");
assertNoTasks();
//...
}
public void testDelete(){
givenAtTodoMVC();
add("a");
delete("a");
assertNoTasks();
}

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

75. End to End Unit/1-feature-per-test
When to use?
+ when start, during
POC for framework
+ in a rush to cover a
lot of existed features
+ for integration
coverage
+ for new features
+ after POC is
approved, on regular
basis

76. Wasn’t it easy? :)

77. Easy tools?

78. Java: Selenide
Python: Selene is coming…
C#: NSelene is coming…
Ruby: Capybara
? JavaScript: Protractor
? PHP: Codeception

79. How to start?
Choose language
Learn language (books, interactive tutorials,
koans, exercism.io, google.com, etc.)
Choose Easy Tools
Find a mentor (friend, dev on your project, it-chats,
forums, etc…)
Go :)

80. 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

81. No ready easy tool for your
language?
Lack of knowledge?
=> ask project’s developers to write it for you
Brave?
=> implement it by your own

82. Afterwords
There are good practices in context,
but there are no best practices.
(c) Cem Kaner, James Bach

83. Q&A

84. github.com/yashaka
youtube.com/c/ItlabsNetUa
gitter.im/yashaka/start-selenium
slideshare.net/yashaka
yashaka@gmail.com@yashaka

85. www.itlabs.net.ua
contact@itlabs.net.ua
+38 (073) 467-61-12
Thank you!