@chrispanag you will need to enter the BrowserStack keys as github secrets for the automated test.

      username: ${{secrets.BROWSERSTACK_USERNAME}}
      access-key: ${{secrets.BROWSERSTACK_ACCESS_KEY}}

@developerphilo can you describe exactly how the tests work here, what happens exactly and what are we testing?

I see two jobs that are doing the same thing (?) pull_request/push

@developerphilo can you describe exactly how the tests work here, what happens exactly and what are we testing?

I see two jobs that are doing the same thing (?) pull_request/push

Browserstack action runs two jobs on push and on pull request but we can configure it to run once though the documentation suggest to run on both push and pull to have a clear depiction against every commit. "We recommend you to run on both push and pull_request so that you have a 1:1 build mapping against every commit".

The action will then invoke a tunnel connection(after grabbing the browserstack secret keys) between our environment and the BrowserStack device cloud. This will allow our app to be accessed by the browsers in the BrowserStack’s device cloud.

what are we testing exactly here?

Also what does the content of browserstack.js does?

what are we testing exactly here?

Also what does the content of browserstack.js does?

We are testing our application on the BrowserStack environment against the browsers in BrowserStack’s device cloud. Basically we are testing our app against various devices and browsers (versions) through BrowserStack.

browserstack.js is the test script hosting the various definitions regarding what browser/screens/version we want to test against. In this file we can declare various browser version and OS to performs our tests on.

We are testing our application on the BrowserStack environment against the browsers in BrowserStack’s device cloud. Basically we are testing our app against various devices and browsers (versions) through BrowserStack.

Yeah, I just meant, what are the success/fail conditions of our tests? Browserstack doesn't know what to test against (I think), or?

We are testing our application on the BrowserStack environment against the browsers in BrowserStack’s device cloud. Basically we are testing our app against various devices and browsers (versions) through BrowserStack.

Yeah, I just meant, what are the success/fail conditions of our tests? Browserstack doesn't know what to test against (I think), or?

We can pass in the browserstack.js various "capabilities" to test against.

We are testing our application on the BrowserStack environment against the browsers in BrowserStack’s device cloud. Basically we are testing our app against various devices and browsers (versions) through BrowserStack.

Yeah, I just meant, what are the success/fail conditions of our tests? Browserstack doesn't know what to test against (I think), or?

We can pass in the browserstack.js various "capabilities" to test against.

As I see, these are just the environments that we'll use for testing. A testing scenario would be: the app initialises without errors or that the app is able to perform the X network requests etc.