René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Configure testing suite","articleBody":"**Motivation**\r\nTesting is a non-negotiable part of developing reliable software.\r\n\r\n**Summary of desired feature**\r\nA test suite and associated CI configuration set up for the project.\r\n\r\n**Design**\r\n\r\n- The tests will be run using pytest.\r\n- The test suite will live in the `tests` directory.\r\n- uv will be used to install pytest and manage dependencies.\r\n\r\n**Describe alternatives you've considered**\r\n- I haven't considered any other testing frameworks than pytest.\r\n- I have found it interesting when working on [pins-python](https://github.com/rstudio/pins-python) that the `tests` folder was inside the package folder. This supports a more modular approach suitable for monorepos, but I don't think it's necessary for this project and quite unconventional.\r\n- Managing dependencies could be done with rye. However, uv is already basically fit for purpose, even though its lockfiles etc. are quite experimental.\r\n\r\n**Testing Strategy**\r\nI would be able to see a successful CI pipeline which runs the testing suite.\r\n\r\n**Steps**\r\n- Configure the project with uv.\r\n- Create a dummy test which just passes trivially.\r\n- Confirm that pytest runs the test successfully from the CLI\r\n- Set up GitHub actions CI pipeline to run pytest on multiple OSs.\r\n\r\n**Acceptance Criteria**\r\nThe CI needs to be able to run at least one test.","author":{"url":"https://github.com/nathanjmcdougall","@type":"Person","name":"nathanjmcdougall"},"datePublished":"2024-08-14T01:35:46.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/3/usethis-python/issues/3"}