[Internal] Integration Testing

datopian / ubdc-data-catalogue-pm

0 stars 0 forks source link

[Internal] Integration Testing #16

Open juanbrits opened 1 year ago

juanbrits commented 1 year ago

Job Story

When I do testing prior to production release, I would like to be able to run automated integration dependencies on some of the basic exercises to test dependencies that are not normally covered with unit testing

Acceptance Criteria

[x] I can run automated tests that can check basic functions such us
[x] Creating a user, logging in, creating an org and dataset
[ ] I can test the restrict public user access
[ ] I can test the resource submission and approval process
[ ] I can test the resource submission and rejection process
[x] The testing methods can be applied to similar CI/CD pipelines

Tasks

[x] Investigate current tests in Cypress
[x] Fix errors
[x] Apply to UBDC CI/CD pipeline
[x] make sure that there is no residual datasets if any test fail

juanbrits commented 1 year ago

Ismail Shahzad:

i looked into cypress testing last night. Some of the tests i fixed. Some are failing. Need to fix those and setting them up in our CI/CD may consume time as i would need to check how they can be added to our google build. I will continue today.

MuhammadIsmailShahzad commented 1 year ago

This has been done. Integration tests are added to staging and prod. On prod we are not creating/adding new datasets and orgs and only checking for the API(s) as adding new datasets was interfering with datacite I believe cc @sagargg

sagargg commented 1 year ago

@MuhammadIsmailShahzad Can we close this issue ? cc @SusanBot85

SusanBot85 commented 1 year ago

Hi @sagargg seems there are still outstanding issues:

As per feedback from @MuhammadIsmailShahzad These two test cases are missing, I think

I can test the resource submission and approval process
I can test the resource submission and rejection process As we have just added general tests for now, not the specific ones for the approval process.

And @sagargg can you provide some feedback on this: on prod we are not creating/adding new datasets and orgs and only checking for the API(s) as adding new datasets was interfering with datacite

sagargg commented 1 year ago

@SusanBot85 I have minimal information on this as @MuhammadIsmailShahzad and @geoffrey13 worked on the implementation.

Yes, we are ignoring any dataset create/update action tests cases on production cuz it is interfering with datacite.