Read about our upcoming Code of Conduct on this issue

Projects: testing webdriver creation with README

As this will be often the first user experience on Heptapod, it
is especially important that it gets its end-to-end test.

Of course, this goes internally through the same method as any
repository file creation, but there wasn't any direct test at
creation time, neither with Selenium, nor with API.

This is again expected to work on GitLab<14.2

--HG--
branch : stable
14 jobs for !97 with topic/stable/webdriver_create_readme in 43 minutes and 35 seconds (queued for 1 second)
latest detached
Status Name Job ID Coverage
  Lint
passed flake8 #243436

00:01:01

 
  Test Heptapod
passed docker-fully-native-inside #243443

00:19:31

passed docker-fully-native-remote-0 #243459

00:15:24

passed docker-fully-native-remote-1 #243445

00:20:49

passed docker-inside #243456

00:15:42

passed docker-native-inside #243440

00:17:58

passed docker-native-remote-0 #243441

00:14:54

passed docker-native-remote-1 #243442

00:20:29

passed docker-remote-0 #243457

00:17:17

passed docker-remote-1 #243458

00:21:42

failed docker-fully-native-remote-0 #243444
allowed to fail

00:01:06

failed docker-inside #243437

00:01:47

failed docker-remote-0 #243438

00:01:02

failed docker-remote-1 #243439

00:00:57