Skip to content

feat(test): Tests implementation#2

Draft
SpacingBat3 wants to merge 6 commits into
masterfrom
feat/tests
Draft

feat(test): Tests implementation#2
SpacingBat3 wants to merge 6 commits into
masterfrom
feat/tests

Conversation

@SpacingBat3

@SpacingBat3 SpacingBat3 commented May 23, 2026

Copy link
Copy Markdown
Owner

Description

This Pull Request aims to implement a testing environment as well as introduce enough tests to describe with them current API. It is still WIP but the test I'll be used will help with the API stabilization, as well as improvements that will reach master branch.

Checklist

  • Implement configuration for tests in CMake
  • Implement a mock library for using C++ std::vector as a reference implementation.
  • Implement tests that will describe the API
    • push for single elements
    • push for arrays
    • push for array concatenation
    • converting arrays to vectors
    • converting vectors to arrays
    • pop operation
    • get operation (explicitly)
    • set operation
    • vector fitting
    • vector scaling
    • etc?
  • Implement performance tests to bench YAVL agains std::vector
    • Benchmark (microbenchmark) push operation for single-element unknown-size pushes, using random data array.
    • etc?

Comment thread test/vec/api/should_convert_arrays.c Fixed
@SpacingBat3 SpacingBat3 changed the title Tests implementation feat(test): Tests implementation May 23, 2026
@SpacingBat3 SpacingBat3 force-pushed the feat/tests branch 3 times, most recently from 6e524f8 to 66f1cc1 Compare June 14, 2026 20:52
I previously was using `int` as the iterator, but switched towards
`size_t`.
Implement generic STDC_NO_THREADS version for tests, so tests may
execute regardless of target platform and compiler limitations.
This uses a combination of CMake and macros to detect and provide more
generic code.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants