Skip to content

Conversation

@treemcgee42
Copy link
Collaborator

Motivation

Currently we don't have (formal) tests that test the user-facing product, that is, test the entire compilation process. Unit tests are important, but it's useful to also have these tests. They are also a useful last-defense against inadvertent breaking changes, particularly when these tests run on multiple platforms.

Summary

Adds the following tests:

  • compiling and verifying output of "hello world" program
  • creating a library providing a function that prints "hello world" and linking to it

Driver tests test the compilation of an entire file or collection
of files, from generating executables to linking libraries. These
are particularly helpful for testing compatibility on different
platforms.
Driver tests test the compilation of an entire file or collection
of files, from generating executables to linking libraries. These
are particularly helpful for testing compatibility on different
platforms.
Driver tests test the compilation of an entire file or collection
of files, from generating executables to linking libraries. These
are particularly helpful for testing compatibility on different
platforms.
@treemcgee42 treemcgee42 marked this pull request as draft January 16, 2024 17:58
@matt-cornell matt-cornell changed the title Add driver tests Add driver tests and figure out why the interner isn't working Jan 25, 2024
@matt-cornell matt-cornell self-requested a review January 25, 2024 20:37
@matt-cornell
Copy link
Collaborator

I don't know why the interner is breaking like this, but we need to fix this before merging.

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.

3 participants