feat(tests): set up automatic testing via github actions #179
+275
−189
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- includes moving header before HTML output to address an error
Draginraptor
approved these changes
Sep 27, 2021
|
After some thinking, I want to look more into writing particular tests... |
- add testing env to gitignore
- rename example unit test so it doesn't fire
itinerare
force-pushed
the
feature/laravel-tests
branch
from
b870150 to
8f25be4
Compare
|
Update.... realized despite the settings being identical to a working setup for some reason it refuses to connect to the mysql instance... I'll leave this here either for myself or another for later but in the meantime I am probably going to move toward writing a test suite for local use, as I have confirmed that that works. |
itinerare
force-pushed
the
feature/laravel-tests
branch
from
8f25be4 to
bd9066d
Compare
itinerare
removed
the
needs review
Conflicts: .gitignore resources/views/layouts/app.blade.php tests/Feature/AccessTest.php tests/Feature/ExampleTest.php
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Runs very basic tests/sees if the app boots on a push or PR to any branch, as well as on publishing of releases; we can build out more/more structured tests down the line if we want, but for the moment it might be enough just to have it ping to make sure basic functionality is there/it can attempt to load... It may be necessary to add some minor checks to views to accommodate this but we can deal with that as needed/appropriate.
From my understanding/testing this works best when implemented across relevant branches? So PRing into master.
I've been working on this for a diff project, so a comparable setup can be viewed in action there.