Setup rake test to run the tests
#11
Conversation
|
Note @joeldrapper on the Quickdraw memory detail |
Gemfile
Outdated
| gemspec | ||
|
|
||
| gem "minitest" | ||
| gem "rspec-expectations" |
There was a problem hiding this comment.
I don't see this being used.
There was a problem hiding this comment.
For some reason, I needed to add this to get the quickdraw runner to work. But I think that was when I was having issues with my installation of Ruby which I scrapped and re-setup. I just tested without these gems, and it works just fine.
|
Love it. One note on the Gemfile I didn't get, but the Rakefile change is lovely. Thank you |
This updates the Rakefile to allow basic running of the tests. However, I found that running the entire test suite eats up all my memory (and then some), and eventually produces errors in the Quickdraw Runner. Because it eats up a bunch of memory, it makes it hard to troubleshoot the Quickdraw error. However, the fact it consumes so much memory for what appears to be a small test suite is probably a bigger issue. The README for Quickdraw itself says it's not ready for production use, so I figured I'd leave the memory issue alone for now. Any additional arguments are passed on to the test runner, so you can do things like `rake test -t 3 test/path/to/testfile.test.rb`. Closes yippee-fun#10
|
@bfad can you open an issue in the Quickdraw repo with some more details? The plume tests run on my laptop in about 600ms, which is faster than ActivityMonitor updates with memory usage. |
I did some more testing on this, and am not going to open an issue about the memory. I was running into the issue in the recent MacOS 26 beta. When I ran the same test on another machine, I did see more memory use than I expected, but nothing like what I was seeing in the beta, and it completed in 16 seconds. For reference, I was calling Do you still want me to note this issue on the Quickdraw repo if it seems limited to a developer beta version of MacOS? |
3 participants
This updates the Rakefile to allow basic running of the tests. However, I found that running the entire test suite eats up all my memory (and then some), and eventually produces errors in the Quickdraw Runner. Because it eats up a bunch of memory, it makes it hard to troubleshoot the Quickdraw error. However, the fact it consumes so much memory for what appears to be a small test suite is probably a bigger issue. The README for Quickdraw itself says it's not ready for production use, so I figured I'd leave the memory issue alone for now.
Any additional arguments are passed on to the test runner, so you can do things like
rake test -t 3 test/path/to/testfile.test.rb.Closes #10