Meta: seriously forked #29

Closed
jaylevitt opened this Issue Apr 19, 2011 · 4 comments

Comments

Projects
None yet
3 participants
@jaylevitt

As a new proto-user of ci_reporter, it seems a bit messy at the moment. The main branch doesn't support Test::Unit 2.0, the readme includes (in addition to this page) a github page that no longer exists, there are many non-converged forks and four open pull requests for different patches. What's the state of the project? Is Nick still leading it, or is someone else working up a new release? I would volunteer to help if I knew what I were doing, but I don't yet; I just want to use Test::Unit (today) and RSpec/Cucumber (tomorrow) with Jenkins CI, and I don't know that that makes me a great help for release. Are there specific tasks that need doing?

@nicksieger

This comment has been minimized.

Show comment Hide comment
@nicksieger

nicksieger Apr 19, 2011

Member

Hi Jay,

I am still the maintainer but have had limited time towards integrating these patches. You're right that there is more demand for Test::Unit 2 support and other fixes.

I'd like to see things get cleaned up, and perhaps I've just been a bit too tight on the reins of the project.

As far as actions, can you do any of the following:

  1. Pull request for README -- send one and if you have questions about what should be fixed let me know in the request
  2. Try integrating one or more of the pull requests and see how they work.

Testing: Ideally (using RVM) we should be able to run on JRuby, Rbx, 1.8.7 and 1.9.2. JRuby and 1.8.7 work fine, Rbx probably as well, but I think 1.9.2 support is lagging partially because of the miniunit/Test::Unit situation.

The code itself might need to be teased apart for different major versions of RSpec, Test::Unit, and so on. The current code (at least for RSpec, for example) is starting to get kludgy in its attempts to support multiple versions.

Thanks for your interest, and let me know if you can help with any of the above.

Member

nicksieger commented Apr 19, 2011

Hi Jay,

I am still the maintainer but have had limited time towards integrating these patches. You're right that there is more demand for Test::Unit 2 support and other fixes.

I'd like to see things get cleaned up, and perhaps I've just been a bit too tight on the reins of the project.

As far as actions, can you do any of the following:

  1. Pull request for README -- send one and if you have questions about what should be fixed let me know in the request
  2. Try integrating one or more of the pull requests and see how they work.

Testing: Ideally (using RVM) we should be able to run on JRuby, Rbx, 1.8.7 and 1.9.2. JRuby and 1.8.7 work fine, Rbx probably as well, but I think 1.9.2 support is lagging partially because of the miniunit/Test::Unit situation.

The code itself might need to be teased apart for different major versions of RSpec, Test::Unit, and so on. The current code (at least for RSpec, for example) is starting to get kludgy in its attempts to support multiple versions.

Thanks for your interest, and let me know if you can help with any of the above.

@jaylevitt

This comment has been minimized.

Show comment Hide comment
@jaylevitt

jaylevitt Apr 21, 2011

How hard do you think it would be to factor out RSpec vs. Test:Unit
into ci_reporter plugins? Maybe the answer is to maintain
ci_reporter as one gem, and support for each test framework as its
own. That way, people can fork off support for newer frameworks
without affecting the old ones, and you won't have as much branch
diversion.
Easy for me to say, anyway.. I'll look at playing with some of the
pull requests this weekend.  How confident do you feel about
ci_reporter's own test coverage? That is, is there more to "see how
they work" than running the test suite and using it a little bit?
Jay

        nicksiegerApril 19, 2011 11:28 AM
      Hi Jay,
      I am still the maintainer but have had limited time towards
      integrating these patches. You're right that there is more
      demand for Test::Unit 2 support and other fixes.
      I'd like to see things get cleaned up, and perhaps I've just
      been a bit too tight on the reins of the project.
      As far as actions, can you do any of the following:
      1. Pull request for README -- send one and if you have
      questions about what should be fixed let me know in the
      request
      2. Try integrating one or more of the pull requests and see
      how they work.
      Testing: Ideally (using RVM) we should be able to run on
      JRuby, Rbx, 1.8.7 and 1.9.2. JRuby and 1.8.7 work fine, Rbx
      probably as well, but I think 1.9.2 support is lagging
      partially because of the miniunit/Test::Unit situation.
      The code itself might need to be teased apart for different
      major versions of RSpec, Test::Unit, and so on. The current
      code (at least for RSpec, for example) is starting to get
      kludgy in its attempts to support multiple versions.
      Thanks for your interest, and let me know if you can help with
      any of the above.
How hard do you think it would be to factor out RSpec vs. Test:Unit
into ci_reporter plugins? Maybe the answer is to maintain
ci_reporter as one gem, and support for each test framework as its
own. That way, people can fork off support for newer frameworks
without affecting the old ones, and you won't have as much branch
diversion.
Easy for me to say, anyway.. I'll look at playing with some of the
pull requests this weekend.  How confident do you feel about
ci_reporter's own test coverage? That is, is there more to "see how
they work" than running the test suite and using it a little bit?
Jay

        nicksiegerApril 19, 2011 11:28 AM
      Hi Jay,
      I am still the maintainer but have had limited time towards
      integrating these patches. You're right that there is more
      demand for Test::Unit 2 support and other fixes.
      I'd like to see things get cleaned up, and perhaps I've just
      been a bit too tight on the reins of the project.
      As far as actions, can you do any of the following:
      1. Pull request for README -- send one and if you have
      questions about what should be fixed let me know in the
      request
      2. Try integrating one or more of the pull requests and see
      how they work.
      Testing: Ideally (using RVM) we should be able to run on
      JRuby, Rbx, 1.8.7 and 1.9.2. JRuby and 1.8.7 work fine, Rbx
      probably as well, but I think 1.9.2 support is lagging
      partially because of the miniunit/Test::Unit situation.
      The code itself might need to be teased apart for different
      major versions of RSpec, Test::Unit, and so on. The current
      code (at least for RSpec, for example) is starting to get
      kludgy in its attempts to support multiple versions.
      Thanks for your interest, and let me know if you can help with
      any of the above.
@nicksieger

This comment has been minimized.

Show comment Hide comment
@nicksieger

nicksieger Apr 21, 2011

Member

Coverage should be pretty good at this point, it's above 95%, I have
rcov tasks in the Rakefile that you can run to see where things aren't
covered. The places are probably where there are RSpec 1/2 API
differences since only one version can run at a time.

/Nick

On Thu, Apr 21, 2011 at 6:01 AM, jaylevitt
reply@reply.github.com
wrote:

How hard do you think it would be to factor out RSpec vs. Test:Unit
   into ci_reporter plugins? Maybe the answer is to maintain
   ci_reporter as one gem, and support for each test framework as its
   own. That way, people can fork off support for newer frameworks
   without affecting the old ones, and you won't have as much branch
   diversion.
   Easy for me to say, anyway.. I'll look at playing with some of the
   pull requests this weekend.  How confident do you feel about
   ci_reporter's own test coverage? That is, is there more to "see how
   they work" than running the test suite and using it a little bit?
   Jay

           nicksiegerApril 19, 2011 11:28 AM
         Hi Jay,
         I am still the maintainer but have had limited time towards
         integrating these patches. You're right that there is more
         demand for Test::Unit 2 support and other fixes.
         I'd like to see things get cleaned up, and perhaps I've just
         been a bit too tight on the reins of the project.
         As far as actions, can you do any of the following:
         1. Pull request for README -- send one and if you have
         questions about what should be fixed let me know in the
         request
         2. Try integrating one or more of the pull requests and see
         how they work.
         Testing: Ideally (using RVM) we should be able to run on
         JRuby, Rbx, 1.8.7 and 1.9.2. JRuby and 1.8.7 work fine, Rbx
         probably as well, but I think 1.9.2 support is lagging
         partially because of the miniunit/Test::Unit situation.
         The code itself might need to be teased apart for different
         major versions of RSpec, Test::Unit, and so on. The current
         code (at least for RSpec, for example) is starting to get
         kludgy in its attempts to support multiple versions.
         Thanks for your interest, and let me know if you can help with
         any of the above.

Reply to this email directly or view it on GitHub:
nicksieger#29 (comment)

Member

nicksieger commented Apr 21, 2011

Coverage should be pretty good at this point, it's above 95%, I have
rcov tasks in the Rakefile that you can run to see where things aren't
covered. The places are probably where there are RSpec 1/2 API
differences since only one version can run at a time.

/Nick

On Thu, Apr 21, 2011 at 6:01 AM, jaylevitt
reply@reply.github.com
wrote:

How hard do you think it would be to factor out RSpec vs. Test:Unit
   into ci_reporter plugins? Maybe the answer is to maintain
   ci_reporter as one gem, and support for each test framework as its
   own. That way, people can fork off support for newer frameworks
   without affecting the old ones, and you won't have as much branch
   diversion.
   Easy for me to say, anyway.. I'll look at playing with some of the
   pull requests this weekend.  How confident do you feel about
   ci_reporter's own test coverage? That is, is there more to "see how
   they work" than running the test suite and using it a little bit?
   Jay

           nicksiegerApril 19, 2011 11:28 AM
         Hi Jay,
         I am still the maintainer but have had limited time towards
         integrating these patches. You're right that there is more
         demand for Test::Unit 2 support and other fixes.
         I'd like to see things get cleaned up, and perhaps I've just
         been a bit too tight on the reins of the project.
         As far as actions, can you do any of the following:
         1. Pull request for README -- send one and if you have
         questions about what should be fixed let me know in the
         request
         2. Try integrating one or more of the pull requests and see
         how they work.
         Testing: Ideally (using RVM) we should be able to run on
         JRuby, Rbx, 1.8.7 and 1.9.2. JRuby and 1.8.7 work fine, Rbx
         probably as well, but I think 1.9.2 support is lagging
         partially because of the miniunit/Test::Unit situation.
         The code itself might need to be teased apart for different
         major versions of RSpec, Test::Unit, and so on. The current
         code (at least for RSpec, for example) is starting to get
         kludgy in its attempts to support multiple versions.
         Thanks for your interest, and let me know if you can help with
         any of the above.

Reply to this email directly or view it on GitHub:
nicksieger#29 (comment)

@shepmaster shepmaster added test-unit and removed 1.7.0 labels Jun 3, 2014

@shepmaster

This comment has been minimized.

Show comment Hide comment
@shepmaster

shepmaster Jun 12, 2014

Member

How hard do you think it would be to factor out RSpec vs. Test:Unit into ci_reporter plugins?

About a full weekend of work. 😄

Member

shepmaster commented Jun 12, 2014

How hard do you think it would be to factor out RSpec vs. Test:Unit into ci_reporter plugins?

About a full weekend of work. 😄

@shepmaster shepmaster closed this Jun 12, 2014

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