facilitate running the testuite in a sandbox
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- lua, nixos
- Domain
- build-system, testing-qa
Research direction
Start by locating the current orgmode test procedure and the make target that prepares the environment before running the command shown in the issue. Separate environment preparation from test execution so a prepared sandbox can run the suite without internet access, then verify both paths with the existing tests.
Written by the indexing model from the issue text.
Description
hi,
I managed to run the testsuite (minus a few tests) for my linux distribution nixos see https://github.com/NixOS/nixpkgs/pull/483694.
The current orgmode test procedure setups the environment (install treesitter grammars and downloads plenary) before running the tests and it's not possible to run separately both. Which is an issue for nix (but certainly other distributions as well) where the build occurs in a sandbox without internet access.
It would be nice to differente between the two so that I can run a make test-with-environment-prepared instead of
nvim --headless -i NONE \
-u test/minimal_init.vim --cmd "set rtp+=${vimPlugins.plenary-nvim}" \
-c "PlenaryBustedDirectory tests { sequential = true, minimal_init = './tests/minimal_init.lua' }"
- Dominant language
- Lua
- Stars
- 3.9k
- Forks
- 192
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 11
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from nvim-orgmode/orgmode
-
Difficulty 1/5 Under an hour Newbie friendliness 73/100
nvim-orgmode/orgmode#1193 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
nvim-orgmode/orgmode#1175 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
nvim-orgmode/orgmode#1173 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 50/100
nvim-orgmode/orgmode#1172 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 62/100
nvim-orgmode/orgmode#1171 ·
Maintainers usually reply within 1 day
All issues in nvim-orgmode/orgmode
Similar issues
-
severity: low
Difficulty 1/5 1-3 hours Newbie friendliness 89/100
luainkernel/lunatik#1980 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
petertriho/nvim-scrollbar#120 ·
-
Addon Conflict Bug Forever Module - Tracker
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day