tarantool / tarantool/tarantool
qa: minimal automatic testing of tarantoolctl rocks
Open
Nobody has claimed this yet.
luarocks
qa
raw idea
tarantoolctl
- Dominant language
- Lua
- Stars
- 3.7k
- Forks
- 419
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 88
Description
Tarantool version: 2.5.0-242-gdaae95869.
We have no automatic tests regarding tarantoolctl rocks command. There are few ideas regarding this:
- I don't know anything about upstream luarocks tests and CI, but they exists and maybe can be reused.
- When we work on update luarocks from 2 to 3, I created the test plan for most used (as I think) functionality and verified it manually. This can be taken as cases for automatic testing.
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 upstream LuaRocks tests and CI, then compare them with the linked test plan for tarantoolctl rocks. Use the plan's most-used functionality as the cases to automate; done means those command paths have repeatable automatic coverage in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- cli, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100