Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test reporting in Ruby #1

Open
hems opened this issue Jun 10, 2013 · 0 comments
Open

test reporting in Ruby #1

hems opened this issue Jun 10, 2013 · 0 comments

Comments

@hems
Copy link
Member

hems commented Jun 10, 2013

When a test is entirely built in Ruby without calling a C++ method, is there a way to inform up the chain that the test passed? Without this, tests look like they are failing during the build script when perhaps they are not. If this is possible, we at least need a demo for the API here:

http://jamoma.org/api-documentation/chapter_unittesting.html

BENEFIT: Such a feature could speed up the development of tests because developer would not need to recompile AND because of this maybe more tests would be created.

SampleMatrix tests are now in C++ here:

https://github.com/jamoma/JamomaDSP/blob/fa7fba6c8e724aa714dafa5b79d256eca74a0e06/library/tests/TTSampleMatrix.test.cpp
https://github.com/jamoma/JamomaDSP/blob/fa7fba6c8e724aa714dafa5b79d256eca74a0e06/Tests/unit/samplematrix.test.rb

But for reference, earlier commits feature testing done more inside Ruby with out reporting via TTTestFinish:

https://github.com/jamoma/JamomaDSP/blob/55ec938dede3c28793d3275c56dc4acff0324114/Tests/unit/samplematrix.test2.rb

see more on the original redmine issue http://redmine.jamoma.org/issues/1207

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant