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

Reach > 90% coverage and add Integration Testing #709

Merged
merged 37 commits into from
Jun 20, 2020
Merged

Conversation

jdalrymple
Copy link
Owner

@jdalrymple jdalrymple commented Apr 22, 2020

  • Added many many more unit tests to increase coverage to 90% +
  • Removed the upsert functionality of PushRules to maintain documented API parity

fixes #686
fixes #698
fixes #309

@jdalrymple jdalrymple changed the title Add Integration Testing Add Integration Testing and Preferring named exports Apr 22, 2020
Copy link
Contributor

@jetersen jetersen left a comment

Choose a reason for hiding this comment

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

LGTM!

@jdalrymple
Copy link
Owner Author

jdalrymple commented Apr 22, 2020

LGTM!

The openpgp tests have been giving me trouble, and we need to verify the typing is correct for the exports.

I thought i had it working, but apparently not. It should take in a dictionary of constructors and return a dictionary of constructors. Any typescript gurus wanna help hehe?

This is what i was referencing the code from

@jdalrymple jdalrymple changed the title Add Integration Testing and Preferring named exports Add Integration Testing Apr 23, 2020
@jdalrymple jdalrymple force-pushed the master branch 2 times, most recently from 09fb950 to 176dadf Compare May 1, 2020 22:09
@jdalrymple jdalrymple force-pushed the integration-tests branch 3 times, most recently from 75a037a to ed23069 Compare May 18, 2020 20:32
@jdalrymple
Copy link
Owner Author

Looks like many parallel calls to the Gitlab instance is resulting in Error 502 Bad Gateway errors. Maybe i have to run these in band?

@jdalrymple
Copy link
Owner Author

jdalrymple commented May 22, 2020

Hmm, how can i change the organization of the tests. Right now when i tests the services in the gitbeaker-node package, none of the files from gitbeaker-core are registered as being covered. I guess since its an imported library. If i moved the tests to gitbeaker-core i would have to defined a requester for the tests, plastically recreating gitbeaker-node just for tests. :/ Ideas?

@jetersen Maybe you have some ideas?

@jetersen
Copy link
Contributor

jetersen commented May 24, 2020

@jdalrymple
Copy link
Owner Author

Ill look into switching it up! @jetersen Any thoughts on the test locations?

@jetersen
Copy link
Contributor

There must be a way in jest to register internal library especially as jest itself is a mono repo. https://github.com/facebook/jest/tree/master/packages

jestjs/jest#3112 (comment)

@jetersen
Copy link
Contributor

jestjs/jest#2418 might be what your looking for.

@jdalrymple jdalrymple changed the title Add Integration Testing Reach > 90% coverage and add Integration Testing Jun 18, 2020
@jdalrymple
Copy link
Owner Author

At 84% so far! only 6% more to go 🙌

@jdalrymple
Copy link
Owner Author

🚀 PR was released in 22.0.0 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants