Skip to content

Commit 9202c15

Browse files
Merge branch 'main' of github.com:applitools/workshop-cbt-selenium-java
2 parents 38f79f5 + aa805ad commit 9202c15

File tree

1 file changed

+13
-14
lines changed

1 file changed

+13
-14
lines changed

README.md

Lines changed: 13 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
![Modern Cross-Browser Testing Workshop](images/modern-cbt-banner.png)
22

3-
# Modern Cross-Browser Testing with Selenium WebDriver in Java
3+
# Modern Cross-Browser Testing with Selenium in Java
44

55
This repository contains the example code for the
66
[Modern Cross-Browser Testing](https://applitools.com/crossbrowser-testing-workshop/) workshop
@@ -12,21 +12,20 @@ Full instructions for the workshop are provided in [`WORKSHOP.md`](WORKSHOP.md).
1212

1313
## Abstract
1414

15-
As organizations double down on digital,
16-
the concept of quality has evolved from "does it work" to "is it the best experience"
17-
— but the race to deliver innovation to market faster than the competition is causing challenges for software teams.
15+
Testing web apps in 2022 is *still* a hard problem.
16+
Apps are more complex than ever,
17+
and their pages must be validated against an exploding number of combinations of browsers, devices, and versions –
18+
an industry average of 81,480 screens to 681,296 for the top 33%.
1819

19-
More frequent releases multiplied by an explosion of device/browser combinations and increased application complexity
20-
has exponentially increased the number of screens that need to be validated each cycle –
21-
an industry average of 81,480 screens to 681,296 for the top 33% –
22-
and traditional test automation can’t keep up.
23-
24-
In this 1-hour interactive workshop
25-
you will learn how industry leaders are integrating cross-browser testing into CI/CD
26-
for faster and immediate feedback.
20+
Old-school tools like Selenium WebDriver still get the job done today,
21+
but old-school techniques for making assertions and running tests across different browsers can't keep up.
22+
Why? They are inherently *sloooooooooow*:
23+
Slow to develop, slow to execute, and slow to maintain.
24+
It's time to rethink how we automate web UI tests at scale for true Continuous Testing.
2725

2826
In this 1-hour workshop,
29-
"Automation Panda" Andrew Knight will explain how to create ultrafast automated cross-browser tests
27+
Pandy Knight, the [Automation Panda](https://automationpanda.com/),
28+
will explain how to create ultrafast automated cross-browser tests
3029
using Applitools Eyes with Selenium WebDriver in Java,
3130
and how to integrate them into CI/CD to provide feedback on quality across all browser/device combinations in seconds.
3231

@@ -36,7 +35,7 @@ and how to integrate them into CI/CD to provide feedback on quality across all b
3635
* The importance and evolution of cross browser testing
3736
* Critical requirements for a scalable cross browser testing initiative and pros/cons of different approaches
3837
* Implementing a modern cross browser solution using Applitools Eyes with Selenium WebDriver in Java
39-
* Accelerating test automation with integration into CI/CD
38+
* Accelerating test automation with integration into CI/CD to achieve Continuous Testing
4039

4140

4241
## Outline

0 commit comments

Comments
 (0)