serlo/frontend-e2e-tests

integration tests for serlo.org

frontend-e2e-tests's Issues

write tests for box plugin

some ideas

handle test cases that are only valid for staging

e.g. impressum at the moment

detect local environment and show output / don't show output

fix e2e tests for enter-behaviour update

add test for geogebra url injection

e.g. https://de.serlo.org/279849

plugin toolbar: in math mode, other options are hidden

this is a change in behaviour and need to be adapted here:

frontend-e2e-tests/tests/400-serlo-editor.ts

Line 719 in 2ea0cd3

I.click('button.serlo-tooltip-trigger.cursor-pointer:nth-child(8)')

RFC: Behavior Driven Development

The way the tests are written now are good for the purpose, but I was thinking if we want to slowly change the way we write to a more BDD-like style.
See https://codecept.io/bdd/#what-is-behavior-driven-development

Instead of using I.click('gerade eben'), I.click('Speicher') we would write I.assertThatRevisionWasNewlyCreated() I.saveMyWork().
Besides that we could use the syntax Given, When, Then.
Pros:

• more readability

Cons:

• more complexity in code

Note:

• another subject of discussion is if we want to change the syntax to use Gherkin (see link above), but let's discuss it after closing this RFC.

run tests with firefox

clicking "Überarbeiten" should check for existing revisions

the current test approach is not reliable, as a failure will leave the system in a bad state.

Probably detect the state and fix it

link to jobs in the footer is using absolute url

again, on localhost this means we are testing staging

add e.g. 5 e2e tests for editor

trying it out + document findings.

Add tests for editor

review config

not quite sure why there are these parameters

Test user flows

Write test cases for registration, verification, recovery and logout.

Testing the OAuth paths will need a different approach and maybe only possible locally (see serlo/local-dev-env).

Update all dependencies https://github.com/serlo/frontend-e2e-tests

add tests for small subject pages

e.g. politk or in other languages

check for secondary menu

editing taxonomy term should show all content types

including exercise folders

Add tests for learner

• single choice / multiple choice
• video, geogebra, injections
• viewing solutions
• taxonomy
• course, course navigation
• exercise folders
• viewing comments
• subject landing pages
• breadcrumbs

flakyness

loading team page is often too slow and will timeout the server

add example of running single script

so I don't have to look it up every time

login not workin

probably related to sso changes.

Make it more reliable.

fix e2e tests for nachhaltigkeit

something changed and the test is breaking - previous fix was not enough ...

Update yarn to latest version in https://github.com/serlo/frontend-e2e-tests

The repository also needs to be migrated to use yarn as a package manager ✨

make test for Team page more robust

even a 20s timeout is not enough ... weird.

make add explicit check for right page and then wait longer after it

Add / check yarn settings in https://github.com/serlo/frontend-e2e-tests

add test cases for comments

write comment

edit comment

archive comment

delete comment

fix e2e test for spanish version

But: It only makes sense if we can actually access the language version!

related to #17

Split the editor tests into multiple smaller files

Currently, there is only one 400-serlo-editor.ts file, and it's almost 1000 lines long. It's time to split it into smaller files, to make it easier to work with the editor tests.

The new files should encapsulate plugins or other UI segments. For example:

400-serlo-editor.ts # Editor loads and all the basic elements are present
410-plugin-toolbar.ts # Plugin toolbar default options
420-plugin-text.ts # Text plugin tests (including plugin toolbar options specific for plugin test)
...

In general, whoever takes the issue can decide how exactly the files should be split and ordered.

Add yarn upgrade-interactive in https://github.com/serlo/frontend-e2e-tests

tests involving language domains are directed to production

there is no good way of going to language domain yet, because we have to change the host, but localhost is on a subdomain (csr is working, though)

add test for images in exercises

as we have here: https://de.serlo-staging.dev/mathe/54749/54749 (even if it's not intended ...)

check for title in add-revision

It should contain "Überarbeiten"

yarn version

@Entkenntnis this uses yarn v1, right?
Should we leave it there or also move to v3?

Set module type to ESM in https://github.com/serlo/frontend-e2e-tests

add test case to check if solution revisions are visible

add test case to check if solution revisions are visible: serlo/frontend#2614