I have no tests for most of this, but since most of them are queries or require very little in the way of manipulating data, it's pretty easy to think that any issues I'll encounter will be because i misstyped something or because MantisConnect doesn't work. A third option is the user fat-fingered or just didn't know what to put in to a field, which I can't help with, yet.
Finding that most of the Mantis features are just not implemented fully in MantisConnect has led me to think that testing from here on out will probably not matter much anyway, since I can't get a full coverage of the features in Mantis as it is. I'll probably regroup on this later, but right now I wnat to get the features I can out there and accessible, since the API is regular enough that I can hope that people would fumble around with it anyway (sorry for them, but I'd rather it work if you know what you're after than not work at all).
…mocha_integration Conflicts: mantisrb.gemspec spec/config_spec.rb spec/projects_spec.rb
After watching a video on Boston Ruby, it is better to wrap your files in a class, so I've done that. Nothing else changed in that instance. Also, minitest 2.6.0 introduced the let syntax to mimic a behavior in RSpec, so I made a change for @session to be a let :session block instead. Not sure about performance on it, but if I can get mocking to work with these tests, it might not matter.
SimpelCov wasn't working properly when I had it just in the spec/spec_helper.rb, so I put the same config lines at the top of my Rakefile, and now it seems that coverage reports work again. Whoo Hoo! Logging wasn't and isn't really useful for specs, so I have it turned off when running specs. I'll figure out something else if I really think I need it later.