Comments (4)
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:
- Pull request for README -- send one and if you have questions about what should be fixed let me know in the request
- 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.
from ci_reporter.
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.
from ci_reporter.
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
[email protected]
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?
JaynicksiegerApril 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:
#29 (comment)
from ci_reporter.
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. 😄
from ci_reporter.
Related Issues (20)
- Add description in the ci_reporter tasks so that rake -T can show them HOT 2
- ci_reporter with rspec and turnip will skip turnip spec HOT 4
- please add source code link to https://rubygems.org/gems/ci_reporter HOT 2
- ci:setup:rspec spec fails and says I have pending migrations HOT 4
- `stderr` and `stdout` capturing is flaky
- ci_reporter alters migration HOT 4
- CI reporter doesn't work with RSpec 3 HOT 5
- Deprecation warnings on Rspec 3. HOT 4
- no such file to load -- ci/reporter/core HOT 1
- Stacktrace on Jenkins spec fail shows error message twice
- XML Reports not generated on Ubuntu HOT 6
- Documentation on writing new formatters does not appear to exist HOT 2
- CI Reporter interfering with Pry? HOT 2
- ci_reporter alters migration #129 HOT 5
- Name of test suite is duplicated in name of test case in the XML reports
- Cannot load such file -- ci/reporter/rake/rspec HOT 2
- release please? HOT 1
- LoadError: no such file to load -- ci/reporter/r_spec3/formatter, trying to use from bundler HOT 2
- Package Name for Jenkins xmlreports Reports HOT 1
- Incompatibility with ruby 3.2.0 onwards HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ci_reporter.