Skip to content
This repository was archived by the owner on Jun 10, 2019. It is now read-only.
This repository was archived by the owner on Jun 10, 2019. It is now read-only.

Wire up automated cross browser testing #113

Open

Description

@rickr

Feature

Why is this feature being added?

Most likely developers are adding features and testing in one browser. We should have an automated check to make sure the functionality is the same across browsers.

What should your feature do?

In a perfect world I would love to see something that upon a new PR (or update to a PR) looks at the files changed and attaches screenshots (or a link to screenshots) of the pages across the major mobile and desktop browsers. Does browserstack cover this or at least come close?

Activity

  1. hollomancer commented on Jun 8, 2017

    @hollomancer
    Member

    Sauce Labs and Browserstack provide functionality like this.

  2. rickr commented on Jun 9, 2017

    @rickr
    ContributorAuthor

    We now have a browserstack account.

    We still need more detail on how this is implemented. Ideally when a new PR comes in we would have browserstack run some tests/take some screenshots and report its status to said PR.

  3. modified the milestone: on Jul 15, 2017
  4. sethbergman commented on Aug 6, 2017

    @sethbergman
    Member

    Do we have a testing framework in mind? Mocha maybe? I know jest is in there by default. I would like to use a good testing library that is easy to write.

    Sent from my Samsung SM-S120VL using FastHub

  5. hollomancer commented on Oct 14, 2017

    @hollomancer
    Member

    Now we just need someone to write some automated UI tests :)

  6. kylemh commented on Oct 22, 2017

    @kylemh
    Member

    #327 💃

  7. kylemh commented on Oct 22, 2017

    @kylemh
    Member

    As for resolving the issue, I think implementing some documentation on using Browser Stack would be good enough to close this.

  8. dmarchante commented on Aug 21, 2018

    @dmarchante
    Contributor

    @kylemh can this be closed due to your testing implementation for the new repo?

  9. kylemh commented on Aug 22, 2018

    @kylemh
    Member

    No. We need the BrowserStack account information @hollomancer

    Once acquired, we can draw up instructions on eyeballing certain browsers on a release basis. We can't exactly share our account out so I think drafting up this methodology is best. It's tough to automate this.

  10. added a commit that references this issue on Oct 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions