Implement first draft of Acceptance Tests #1392
Open
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
timofurrer
force-pushed
the
feature/acceptance-tests
branch
from
b231491
to
59d332a
Compare
|
@svanharmelen do you have some time to sync on this next week? |
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.
I took a stab at implementing some basic form of Acceptance Tests which run against a real GitLab instance.
They are located in the
acc/directory. They run against a GitLab CE instance, but also a GitLab EE instance can be used given that you own license. I've wrote a brief contributing file to document this.I'm not really sure if that's the best way yet to structure this, but I think it's already a valuable start.
We are actually using a pretty similar setup in the GitLab terraform provider.
@svanharmelen please let me know what you think ;)