IQSS / IQSS/dataverse-client-javascript
Add an isolated functional testing mechanism
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 20
- Forks
- 11
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 1
Description
Overview of the feature request
Add a functional testing mechanism for the use cases of the package that helps in the review and QA process of the PRs, so that the use cases can be tested in isolation, without having to depend on other repositories like the dataverse-frontend to prove that the use cases consumption works from a functional perspective.
These tests would help to verify that use cases can be imported with no issues, as stated in this comment: https://github.com/IQSS/dataverse-client-javascript/pull/116#issuecomment-1907711330
What inspired the request?
Retrospective action item.
What existing behavior do you want changed?
None
Any brand new behavior do you want to add to js-dataverse?
None
Any open or closed issues related to this feature request?
None
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the package's use cases and the linked pull request comment about importing them without issues. Identify how the repository currently runs tests and define an isolated mechanism that exercises use-case consumption without another repository. Done means the use cases can be functionally tested during pull-request review and QA.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100