Test Conda components harvest

clearlydefined / crawler

A service that crawls projects and packages for information relevant to ClearlyDefined

MIT License

43 stars 30 forks source link

Test Conda components harvest #568

Open qtomlinson opened 2 weeks ago

qtomlinson commented 2 weeks ago

This documents the QA work that is required for the implementation of Conda component harvest:

Trigger harvest and verify that component is harvest correctly case 1. coordinates with version specified, case 2. latest version of component when version is not specified
related source component correctlly identified and harvested
Verify definition correctly computed: case 1, license detected in scancode package information. case 2 if license not detected in scancode package level, figure out license based on license files in /info directory.
Add integration test add a test case (coordinates) in testConfig.js + fixture for Conda in operation repo

qtomlinson commented 2 weeks ago

@lisahoong Please feel free to add on the cases that you can think of. Appreciate your help!

qtomlinson commented 2 weeks ago

Following our code review discussion, I would like to suggest testing the impact of implementing caching indexes (specifically repodata.json and channeldata.json) on the service's performance. This can be done by calling the /originConda endpoint to query Conda components. This can be currently tested on service dev deployment

qtomlinson commented 1 week ago

Integration Test Readme can be helpful. Please also feel free to put up a PR to enhance it for others. Sample PR might be helpful for adding an integration test case. All the test components are tested in definitionTest.js and attachmentTest.js. When there are attachments in your test definition, more fixtures may need to be added and loaded for the attachmentTest.js.

lamarrr commented 1 day ago

the tests have been added to https://github.com/clearlydefined/operations/pull/72/ and verified