extract autotest support to an rspec-autotest gem #285

Closed
dchelimsky opened this Issue Jan 21, 2011 · 8 comments

Comments

Projects
None yet
4 participants
@dchelimsky
Member

dchelimsky commented Jan 21, 2011

No description provided.

@myronmarston

This comment has been minimized.

Show comment
Hide comment
@myronmarston

myronmarston Dec 24, 2012

Member

@dchelimsky -- I agree 100% with the goal to remove autotest-related code from rspec-core, but it seems like most of the community has moved on to guard and/or watchr at this point--so I'm wondering if we need to preserve the code in a gem at all? (I admit I've never been an autotest user and am not totally sure what extra integration rspec is providing here that a user couldn't easily get on their own using public autotest APIs).

If we do move it into a separate gem, I'd want it to have a "not maintained" notice -- the main thing I'm concerned about here is adding another gem we need to maintain. Extracting it and doing one release to get it out there wouldn't be too bad, though.

Member

myronmarston commented Dec 24, 2012

@dchelimsky -- I agree 100% with the goal to remove autotest-related code from rspec-core, but it seems like most of the community has moved on to guard and/or watchr at this point--so I'm wondering if we need to preserve the code in a gem at all? (I admit I've never been an autotest user and am not totally sure what extra integration rspec is providing here that a user couldn't easily get on their own using public autotest APIs).

If we do move it into a separate gem, I'd want it to have a "not maintained" notice -- the main thing I'm concerned about here is adding another gem we need to maintain. Extracting it and doing one release to get it out there wouldn't be too bad, though.

@dchelimsky

This comment has been minimized.

Show comment
Hide comment
@dchelimsky

dchelimsky Dec 24, 2012

Member

re: maintenance, there is very, very little. I'd either commit to maintaining, find someone else to commit to it, or leave it as/is.

Member

dchelimsky commented Dec 24, 2012

re: maintenance, there is very, very little. I'd either commit to maintaining, find someone else to commit to it, or leave it as/is.

@myronmarston

This comment has been minimized.

Show comment
Hide comment
@myronmarston

myronmarston Dec 24, 2012

Member

By "leave it as/is" do you mean leave the code in rspec-core? Or extract the code into an external gem, and then leave as-is in that gem?

Member

myronmarston commented Dec 24, 2012

By "leave it as/is" do you mean leave the code in rspec-core? Or extract the code into an external gem, and then leave as-is in that gem?

@dchelimsky

This comment has been minimized.

Show comment
Hide comment
@dchelimsky

dchelimsky Dec 24, 2012

Member

I mean just leave it in rspec-core. I think minitest should be supported. Guard is supported by that project, so we don't need to worry about it.

Member

dchelimsky commented Dec 24, 2012

I mean just leave it in rspec-core. I think minitest should be supported. Guard is supported by that project, so we don't need to worry about it.

@JonRowe

This comment has been minimized.

Show comment
Hide comment
@JonRowe

JonRowe Apr 1, 2013

Member

I'd favour removing autotest support to a separate gem, mainly because ZenTest is a PITA. Most people I know moved onto autotest-standalone and then guard to avoid it.

Member

JonRowe commented Apr 1, 2013

I'd favour removing autotest support to a separate gem, mainly because ZenTest is a PITA. Most people I know moved onto autotest-standalone and then guard to avoid it.

@cupakromer

This comment has been minimized.

Show comment
Hide comment
@cupakromer

cupakromer Jun 16, 2013

Member

I'm probably one of the remaining few who still use autotest. I like it because I can have it installed locally and it works without messing with the rest of the project (Guard adds it's own config file). However, that being said, I'm pretty much the only person in the projects I'm involved in who uses it. My co-workers don't have an alternative, they just manually run tests.

That being said I have no real preference if it says or goes. If it makes life easier, I'm 👍 for removal.

Member

cupakromer commented Jun 16, 2013

I'm probably one of the remaining few who still use autotest. I like it because I can have it installed locally and it works without messing with the rest of the project (Guard adds it's own config file). However, that being said, I'm pretty much the only person in the projects I'm involved in who uses it. My co-workers don't have an alternative, they just manually run tests.

That being said I have no real preference if it says or goes. If it makes life easier, I'm 👍 for removal.

@JonRowe

This comment has been minimized.

Show comment
Hide comment
@JonRowe

JonRowe Jun 16, 2013

Member

Just FYI, we are planning to extract support for autotest from rspec into a separate gem come the release of rspec 3

Member

JonRowe commented Jun 16, 2013

Just FYI, we are planning to extract support for autotest from rspec into a separate gem come the release of rspec 3

@myronmarston

This comment has been minimized.

Show comment
Hide comment
@myronmarston

myronmarston Aug 14, 2013

Member

Closing as @JonRowe has done this.

Member

myronmarston commented Aug 14, 2013

Closing as @JonRowe has done this.

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