Skip to content

UI Tests Failing #1717

@mokagio

Description

@mokagio

This is a reference issue to explain why the UI tests fail and why we are not fixing them at this time.

Why they fail

As @AliSoftware recently observed:

The UI Tests CI job is failing because it seems it doesn't find the JSON used to handle test accounts used for those UI Tests

This seems unrelated to the changes in this PR and more likely related to the URL we used to store those not being valid anymore (hence the body of the request being just the text Not Found instead of the expected JSON, leading to JSON parsing error)

The value of UI_TESTS_ACCOUNTS_JSON_URL env var—as provided via .mobile-secrets—is a URL to https://kvdb.io/<someid>/… so I guess maybe our subscription to that service expired or something? (though I haven't found credentials for such service in Secret Store, so unable to verify)

Why we are not fixing them

At this time, we have very little bandwidth for Simplenote work. One would argue that having automated tests working is even more valuable then, but in the wider scheme of things, fixing these tests that only run occasionally is less valuable that helping other teams move forward.

Moreover, fixing is unlikely to be a matter of loosening a timeout or updating an API. This adds to the difficulty of finding enough time for it.

We hope things will change at some point and we'll have time for a deeper dive to address the issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions