-
Notifications
You must be signed in to change notification settings - Fork 203
Open
Labels
needs discussionThis feature request needs discussion, or this bug needs discussion about the solutionThis feature request needs discussion, or this bug needs discussion about the solution
Description
Checklist
- I have searched the issue tracker for relevant or duplicate issues.
I want to suggest some general feature
See a1fd324
Topgrade should have integration tests run in CI for each step, where the step is actually ran and verified that an update happened
Integration tests should be placed in the same file as the step (we probably want to split each step into its own file before starting on integration tests).
Integration tests should be ran only in CI or a container or whatever. Ideally they should be ran as normal cargo tests, but with a certain flag active? Then it should be made really clear not to use to flag on your dev machine.
A test for a step should roughly consist of the following:
- Install the thing it should update (e.g. a package manager and a single package), with a specific old version
- Verify version == old
- Run
topgrade --only that_step, check success - Verify version > old (latest)
- Run
topgrade --only that_step, check success - Verify version == version from step 4
Metadata
Metadata
Assignees
Labels
needs discussionThis feature request needs discussion, or this bug needs discussion about the solutionThis feature request needs discussion, or this bug needs discussion about the solution