Skip to content
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

Add initial acceptance test structure and first test #150

Merged
merged 34 commits into from
Sep 1, 2020

Conversation

sherifnada
Copy link
Contributor

@sherifnada sherifnada commented Sep 1, 2020

What

  1. Adds acceptance test structure and the first acceptance test.
  2. Runs acceptance tests on merge to master (not branches). and notifies in Slack if build fails.

How

  1. Add the dataline-acceptance-tests gradle subproject. This module's tests are run only when explicitly requested, and not as part of the main build.
  2. Add first acceptance test (test the creation of a source implementation).
  3. Run acceptance tests on merge to master.

Recommended reading order

  1. dataline-acceptance-tests/build.gradle
  2. tools/bin/build.sh
  3. .gradle.yml
  4. AcceptanceTests.java

@sherifnada sherifnada marked this pull request as ready for review September 1, 2020 18:05
@sherifnada sherifnada linked an issue Sep 1, 2020 that may be closed by this pull request
.workspaceId(defaultWorkspaceId)
.connectionConfiguration(dbConfiguration);

SourceImplementationRead createResponse = callApi("source_implementations/create", sourceImplementationCreate, SourceImplementationRead.class);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we could generate a client from the oas definition. that will also help catch name changes if they happen

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will look into this

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This hasn't been 100% straightforward, going to do this in a following PR so Jared can work off of this module

testImplementation "org.testcontainers:testcontainers:1.14.3"
testImplementation "org.testcontainers:postgresql:1.14.3"
testImplementation "org.postgresql:postgresql:42.2.16"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

isn't it better when it is sorted?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there a plugin that will sort this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Found this. Might toy around with it but generally I don't find myself spending any meaningful time reorganizing deps

Copy link
Contributor

@jrhizor jrhizor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. I'd prefer for the module to be a more general name like dataline-tests or something which includes integration-specific as well as end to end tests.

@sherifnada sherifnada merged commit 7424ac3 into master Sep 1, 2020
@sherifnada sherifnada deleted the sherif/e2e-structure branch September 1, 2020 21:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add end-to-end tests
4 participants