IronCoreLabs / IronCoreLabs/ironhide
Test suite
- Dominant language
- Rust
- Stars
- 53
- Forks
- 5
- Avg merge
- 41m
- Merged PRs (30d)
- 2
Description
Create a test suite that replicates [the one we've lost](https://github.com/IronCoreLabs/ironhide/tree/46bdf5bc67c3773dcfedb8bd6dd7417b520494a2/test).
We could accomplish this with secrets containing keys generated for a test user that would allow for full functionality of a user to test inputs and outputs against the IronCore service. This would probably the most useful set of tests as far as confirming end user functionality, but they'd be integration tests.
Another option would be to do what the original tests did and mock responses from the IronCore service, unit testing that expected commands function, send calls to the expected REST endpoints, and display the expected results given the canned responses. This may be harder given current Rust tooling.
https://bitheap.org/cram/
https://github.com/assert-rs/trycmd
https://crates.io/crates/snapbox
https://crates.io/crates/assert_cmd
https://crates.io/crates/assert_fs
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by comparing the current repository with the lost test suite at test in commit 46bdf5bc67c3773dcfedb8bd6dd7417b520494a. Evaluate the integration-test and mocked-response approaches, including cram, trycmd, snapbox, assert_cmd, and assert_fs. Done means the chosen approach covers the intended command inputs, REST calls, and outputs, with a documented way to run the suite.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100