Test passes, but doesn't on GitHub via GitHub actions

From the local suite or the Github suite?

for your remote tests.

@fideloper https://pastebin.com/QWT0Xbaa

The "errors" from the tests are passing locally.

Gotcha -

What I would do is take one of those specific tests that are failing (throwing a 500 error instead of expected 200) and add $this->withoutExceptionHandling(); in the beginning of that test.

Then push that change up so GH actions runs it. You should then get some real error output that's more useful there to let you know what's going on.

Another solution may be to generate an artifact out of your laravel.log file so you have that to review when the build is fails. That's a big more complicated but not too bad:

1. you'll need an action to run on failure and then
2. use this action to download the laravel log file as an artifact

But the first solution there to remove exception handling (and thus get a full exception stack trace output in your failing test) might be easier.

@fideloper you're a life saver... was wondering what was wrong since 4 hours

@fideloper That was actually really helpful. I had the same issue as the author - getting 500 errors in the pipeline for all my "expect ABC screen to be rendered" tests. Turns out, that after applying $this->withoutExceptionHandling(); I got the error message that some Vite manifest was missing at /public/build/....

I tested it locally by removing the /public/build directory (since I can always rebuild it with npm run build) and ran my tests -> GOTCHA - same errors locally.

Fix:

Simply add some npm commands into your GitHub action, e.g.:

  - name: Setup Node.js
    uses: actions/setup-node@v2
    with:
      node-version: '20.10.0'

  - name: Install npm dependencies
    run: npm ci

  - name: Build assets
    run: npm run build

Et voilá! Tests succeed :)