Skip to content

[hold] Bug: Randomly failing E2E tests #376

@wishfulthinkerme

Description

@wishfulthinkerme
Contributor

Expected Results

Stop E2E from failing randomly.

Observed Results

Randomly, random tests are failing locally and in the pipeline. There isn't any case, which this can be reproduced. Sometimes it works, sometimes not. We have to check if that is caused by our E2E tests, connection issues or backend problems.

Activity

added
CITasks related to the CI, pipeline, and releasing
on Nov 22, 2018
added this to the ALPHA-0 milestone on Nov 27, 2018
Xymmer

Xymmer commented on Dec 5, 2018

@Xymmer
Contributor

moving this back in, gil is saying this still happens, sometimes, with the server;
Marcin, i can't remember why we moved this to done, do you?

wishfulthinkerme

wishfulthinkerme commented on Dec 6, 2018

@wishfulthinkerme
ContributorAuthor

I couldn't reproduce random failing, so we decided to move it to the done for now.

removed their assignment
on Dec 7, 2018
marlass

marlass commented on Dec 11, 2018

@marlass
Contributor

First we need to resolve the issue with wrong backend payment url.

Xymmer

Xymmer commented on Dec 11, 2018

@Xymmer
Contributor

hey marcin, e2e fixed, can you resume investigation?

marlass

marlass commented on Dec 18, 2018

@marlass
Contributor

I looked at it for a few hours and could found the real issue. Failures are completely random. One time some test fail and then it works for few runs. In the meantime, another one fails and the story repeats. Will look more at this issue in next weeks and might check some alternatives to protractor that are much more stable and easier to debug and work with. Current solution slows whole development too much. We lose way to much time on triggering pipelines and the process of writing tests is also not efficient. We need to check our work line by line and writing whole tests that just runs in the first try is almost impossible. After finding some better replacement I will introduce it to a wider audience and we will decide the e2e tests future in the project.

13 remaining items

added this to the BETA-0 milestone on Mar 11, 2019
modified the milestones: 1.0 Beta-0, 1.0 RC-0 on Apr 25, 2019
modified the milestones: 1.0 RC-0, 1.? Milestone TBD on May 22, 2019
Xymmer

Xymmer commented on May 24, 2019

@Xymmer
Contributor

no longer needed as we moved from protractor to cypress

added this to the before-5.0 milestone on Jun 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

CITasks related to the CI, pipeline, and releasingbugSomething isn't workinge2e-teststeam/asterix

Type

No type

Projects

No projects

Relationships

None yet

    Development

    No branches or pull requests

      Participants

      @hackergil@Xymmer@dunqan@marlass@wishfulthinkerme

      Issue actions

        [hold] Bug: Randomly failing E2E tests · Issue #376 · SAP/spartacus