You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it's important to have tests for all the functionality we have so far. First thing's first though: we should decide on a testing gem. I see you've added minitest, but I also saw ruby/rails is not your native coding language. I prefer rspec personally, because of the style of how the tests are writen.
The text was updated successfully, but these errors were encountered:
I think that's a good idea, unfortunately I've not a lot of experience in that area with either framework. Essentially, at this point this project is somewhat of a playground and a learning platform for me. While there is some basic functionality supported, I've not yet nailed down the exact featureset that I want to support. Feel free to follow up with examples of what you think might be best. Minitest was just the testing framework that was the default when creating the gem with bundler, so if you have better experience in another framework I'm open to switching.
I think it's important to have tests for all the functionality we have so far. First thing's first though: we should decide on a testing gem. I see you've added minitest, but I also saw ruby/rails is not your native coding language. I prefer rspec personally, because of the style of how the tests are writen.
The text was updated successfully, but these errors were encountered: