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

expected passing and known/expected failing integration tests #4438

Closed
pameyer opened this issue Jan 26, 2018 · 1 comment
Closed

expected passing and known/expected failing integration tests #4438

pameyer opened this issue Jan 26, 2018 · 1 comment
Assignees

Comments

@pameyer
Copy link
Contributor

pameyer commented Jan 26, 2018

From http://irclog.iq.harvard.edu/dataverse/2018-01-26#i_62551; the "source of truth" for which integration tests are regularly run (and expected to pass) isn't publicly visible (readme for docker all-in-one integration test instructions is also out of date, apparently). At the moment, expected passing ones are: DataversesIT,DatasetsIT,SwordIT,AdminIT,B​uiltinUsersIT,UsersIT,UtilIT,ConfirmEmailIT,File​MetadataIT,FilesIT,SearchIT,InReviewWorkflowIT.

Running with -Dtest='*IT' attempts to run all integration tests, including some that are expected to fail with current codebase / integration test setup configuration (BatchImportIT,GeoconnectIT,ThumbnailsIT,DataCaptureModuleServiceBeanIT,S3AccessIT). No luck so far with wildcard/regex CLI options to exclude these (potentially org.junit.Ignore annotation).

@pameyer
Copy link
Contributor Author

pameyer commented Mar 9, 2018

HarvestingServerIT ; assuming that #4096 is accepted

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

No branches or pull requests

4 participants