public inbox for ~johnnyrichard/olang-devel@lists.sr.ht
 help / color / mirror / code / Atom feed
From: Johnny Richard <johnny@johnnyrichard.com>
To: Carlos Maniero <carlos@maniero.me>
Cc: ~johnnyrichard/olang-devel@lists.sr.ht
Subject: Re: [PATCH olang 2/2] tests: add integration test setup
Date: Fri, 16 Feb 2024 09:17:02 +0100	[thread overview]
Message-ID: <2tf46gbtznj63ffzokimrpzvq3lyiqekwehvtd5yb67u4lunyy@u7h6lun7iiuf> (raw)
In-Reply-To: <CZ65CAVNEPLF.OFWGZUHBQA51@maniero.me>

Thanks for the reply.

On Thu, Feb 15, 2024 at 11:27:00PM -0300, Carlos Maniero wrote:
> > What is the motivation behind segregate integration tests from unit
> > tests?
> 
> I might be dreaming at this point, but I know you kinda share the same
> dream of making olang a self-hosted language. With this in mind, I think
> it is a good idea to have these two levels of testing: unit tests will
> test c-related stuff and implementation details, while integration tests
> will test the compiler features by calling the compiler with a
> *system()* call.
> 
> When we start to rewrite the compiler in olang, the unit tests may
> change because we gonna change the design of the compiler to remove the
> "c-accent". On the other hand, integration tests should not be touched
> during the rewriting process because the features will stay the same.

Yeah, we do share the same dream :), but maybe is too early to optimize
it.  In the end, everything is a binary, and we are using Makefile to
run the tests, I cannot see any problem on having two different
languages within test folder.

Anyhow we can keep it like this.  I don't have a strong opinion to be
honest.

> > What is binary_loc? Does it means location or path?
> 
> Yeah! that name sucks. It is the compilation result binary path.
> WDYT about rename it to *program_path*?

I think /loc/ also works. I was trying to confirm if I understood
correctly.  But sure, /program_path/ is clearer.

> And sorry about the previous empty email, I've no idea what happened.

No worries.

      reply	other threads:[~2024-02-16  7:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-15 16:21 [PATCH olang 0/2] Add integration tests Carlos Maniero
2024-02-15 16:21 ` [PATCH olang 1/2] tests: add munit testing framework file Carlos Maniero
2024-02-15 16:21 ` [PATCH olang 2/2] tests: add integration test setup Carlos Maniero
2024-02-15 16:27   ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-15 22:21   ` [PATCH olang 2/2] tests: add integration test setup Johnny Richard
2024-02-15 22:07     ` Carlos Maniero
2024-02-16  2:27     ` Carlos Maniero
2024-02-16  8:17       ` Johnny Richard [this message]

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=2tf46gbtznj63ffzokimrpzvq3lyiqekwehvtd5yb67u4lunyy@u7h6lun7iiuf \
    --to=johnny@johnnyrichard.com \
    --cc=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