Skip to content

Feature/#39 - Acceptance Tests #389

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

NullVoxPopuli
Copy link
Contributor

@NullVoxPopuli NullVoxPopuli commented Aug 29, 2018

I believe this maybe fully fulfills the acceptance tests criteria of #378

@NullVoxPopuli NullVoxPopuli changed the title work on adding tests for different scenarios WIP: work on adding tests for different scenarios Aug 29, 2018

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
…d records

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
@NullVoxPopuli NullVoxPopuli changed the title WIP: work on adding tests for different scenarios Work on adding tests for different scenarios Aug 30, 2018
@NullVoxPopuli NullVoxPopuli changed the title Work on adding tests for different scenarios Feature/#39 - Acceptance Tests Aug 30, 2018
@jaredcnance jaredcnance merged commit a8031c6 into json-api-dotnet:feat/#39 Sep 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants