public inbox for ~johnnyrichard/olang-devel@lists.sr.ht
 help / color / mirror / code / Atom feed
From: Carlos Maniero <carlos@maniero.me>
To: ~johnnyrichard/olang-devel@lists.sr.ht
Cc: Carlos Maniero <carlos@maniero.me>
Subject: [PATCH olang 0/2] add unit tests config
Date: Sat, 17 Feb 2024 21:27:11 -0300	[thread overview]
Message-ID: <20240218002713.3705605-1-carlos@maniero.me> (raw)

Simple configurations to start supporting unit tests.

Note that I moved the munit to a shared directory to avoid having it
duplicated over te codebase. Although I kept the .o duplicated in each
folder it is used so then It won't requires any extra configuration to
clean the munit.o. The make clean of both integration and unit will
handle the cleaning.

Carlos Maniero (2):
  tests: move munit to a shared directory
  tests: add unit tests configuration

 Makefile                              |  6 +++++-
 tests/integration/Makefile            | 16 +++++++++------
 tests/{integration => shared}/munit.c |  0
 tests/{integration => shared}/munit.h |  0
 tests/unit/Makefile                   | 28 +++++++++++++++++++++++++++
 5 files changed, 43 insertions(+), 7 deletions(-)
 rename tests/{integration => shared}/munit.c (100%)
 rename tests/{integration => shared}/munit.h (100%)
 create mode 100644 tests/unit/Makefile

-- 
2.34.1


             reply	other threads:[~2024-02-18  0:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-18  0:27 Carlos Maniero [this message]
2024-02-18  0:50 ` [PATCH olang 1/2] tests: move munit to a shared directory Carlos Maniero
2024-02-18  0:50   ` [PATCH olang 2/2] tests: add unit tests configuration Carlos Maniero
2024-02-18  0:55     ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-19  0:50 ` [PATCH olang 0/2] add unit tests config Johnny Richard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240218002713.3705605-1-carlos@maniero.me \
    --to=carlos@maniero.me \
    --cc=~johnnyrichard/olang-devel@lists.sr.ht \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.johnnyrichard.com/olang.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox