first crack at some testing#64
Conversation
|
This is really cool! Reading up on jest now :o |
|
Should devise a way to preconfigure the gitlab build to already have a token available |
|
Yup, agreed. Wanted to make sure the rest of the approach seems good before spending too much time on it. |
|
The only thing I'd change is the folder structure, and maybe switching to a tap reporter because I for some reason really like tap 🤣 but besides that looks really good. Would travis ci then be responsible for spinning up the gitlab instance through docker compose and then running the library against it. Or would the getting the library into the container also be part of a docker compose file ? |
|
I added more tests to the gitlabci branch! 😄 |
|
Weird, tried to merge my changes into your remote branch and that autoclosed the PR. hmmm |
This is by no means intended to be merged. This was just meant to get a starting point out there and see what you think. Added some brief words on the readme about how to fire it up for testing. I'm using
jestto run the tests which is what we use at work all the time so it's just what I'm familiar with. Otherwise this is a super basic test just proving out that it can run and hit the dockerized gitlab.