TopoToolbox / TopoToolbox/libtopotoolbox

Improve the test infrastructure

Open
#55 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

test
Dominant language
C
Stars
2
Forks
11
PR merge metrics
No merged PRs in 30d

Description

While working on #23, I have run into some challenges because of our messy testing setup. The property-based testing approach seems to work well but there are a few things that need to be improved:

  • Make adding a new property to a test significantly simpler, with less boilerplate.
  • #159
  • #158
  • #150
  • #56
  • #96
  • #97
  • Document the testing architecture (see #94)
  • #59
  • #61

It might be worthwhile to use an existing testing framework like GoogleTest, but I do not yet know enough about those to make an informed decision.

Contributor guide

Open the contributing guide

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.

Research direction

Start by reading issue #23 and the remaining unchecked items, especially #159, #158, and #150. Compare the current property-based testing approach with the GoogleTest option mentioned here, then define a focused testing-infrastructure scope and a concrete completion criterion before making changes.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.