Open
Conversation
So that you can write ./factor-tests -i=/foo/bar/factor.image. Also a comment explaining how the test suite should be compiled and run.
Member
|
So I like this idea but I noticed hard coded paths to |
Member
Author
|
I'm not sure. You can override the paths using |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Here is a small test suite for the VM I've been working on. Testing that things like garbage collection works is often too hard to do in Factor code. I based it on googletest (https://code.google.com/p/googletest/) because it seemed simple enough (although there are 5e9+ other c++ test frameworks to choose from).