replace shindo

[geemus]

shindo is weird and a barrier to contribution/updates. Seems like it might be good to migrate. These days I'm somewhat leaning toward rspec with assertions (not #should).

[nextmat]

👍 I think this would be a good move.

[nextmat]

Also I'd be up for tackling some of this but if so I'd like to work in chunks as I think the burden of tracking along w/ other changes would lead to an unpleasant monster-merge. What do you think?

[geemus]

Yeah. Doing it in chunks seems most tenable, especially in terms of other movement. That said, ideally we wouldn't have to support both suites for an extended period, as that has it's own nastiness.

[nextmat]

Agreed, I'm with you on that.

[bjeanes]

@geemus does your renaming of this issue away from minitest? indicate a change in preference or just a general restating of goals? If I or @kahlouie were to start working on an alternate test suite, do you have a strong preference for testing library used?

[geemus]

@bjeanes a fine question. It is somewhat of both I think (change of preference and restatement). I'm leaning somewhat toward rspec due to it having a more active (and welcoming) community around it. I like the minimality of minitest, but not method-named-tests nor the relatively closed/unwelcoming community I've found there. Happy to discuss further though.

[bjeanes]

Sounds good to me. I've been using minitest in new projects of mine for simplicity reasons, but RSpec is a fine choice given the mentioned constraints.

[geemus]

@bjeanes yeah. I definitely know of pros/cons in both columns, but leaning toward rspec at least slightly at present due to more active development/community.

[geemus]

Close in favor of #575