Cleanup of LuaJIT test suite

Open
#129 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
12/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
lua
Domain
testing

Research direction

The cleanup work is meant to happen in the separate LuaJIT-test-cleanup repository, not in this one, and the scope of the merge-back is still marked TBD in the issue. Start with the linked access issue in that repository to see what is already decided. This issue would only be done once the cleanup is finished and merged flat, so a newcomer should not start here.

Written by the indexing model from the issue text.

Description

help wanted

I've just added: https://github.com/LuaJIT/LuaJIT-test-cleanup

The intention is that all cleanups and refactoring should happen over there. Please discuss everything needed for this to happen over there. Feel free to open issues as needed. Anyone who wants commit access, please see: https://github.com/LuaJIT/LuaJIT-test-cleanup/issues/1

When everything is done, it should be merged into this repo 'flat', without the history. The cleanup history will be quite messy and not very useful here. [TBD whether this is to be merged or split off, too.]

Dominant language
C
Stars
5.8k
Forks
1.2k
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from LuaJIT/LuaJIT

All issues in LuaJIT/LuaJIT

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.