Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.ruby > #3123 > unrolled thread

Hook into rake for reporting results

Back to article view | Back to comp.lang.ruby

Contents

  Hook into rake for reporting results milki <milki@rescomp.berkeley.edu> - 2011-04-18 16:48 -0500
    Re: Hook into rake for reporting results Steve Klabnik <steve@steveklabnik.com> - 2011-04-18 17:44 -0500
      Re: Hook into rake for reporting results milki <milki@rescomp.berkeley.edu> - 2011-04-19 08:17 -0500
        Re: Hook into rake for reporting results Steve Klabnik <steve@steveklabnik.com> - 2011-04-19 08:45 -0500
    Re: Hook into rake for reporting results Michael Sokol <mikaa123@gmail.com> - 2011-04-18 19:05 -0500
      Re: Hook into rake for reporting results milki <milki@rescomp.berkeley.edu> - 2011-04-19 08:17 -0500

#3123 — Hook into rake for reporting results

Hi,

I'm building an integration tool between software projects and issue
trackers. What would be the best way to report test success/failures
from a ruby project?

I would need to be able to individually identify which tests
failed, passed, or are pending (success on expected failures and fail if
passing on an expected failure).
I would also like to have minimal modifications if I wanted to add this
tool to an existing ruby project.
A report could either be written to a file or execute custom code to
interact with another software package.

From what I have found, it would be best to hook into the rake system
either via a custom runner or formatter. There isn't too much
documentation on either of these so I'm not sure if this is the right
way.

Any suggestions?

Thanks.
milki

[toc] | [next] | [standalone]

#3125

[Note:  parts of this message were removed to make it a legal post.]

If I was you, I'd look at the code for minitest and or simplecov/rcov.

[toc] | [prev] | [next] | [standalone]

#3168

On 07:44 Tue 19 Apr     , Steve Klabnik wrote:
> If I was you, I'd look at the code for minitest and or simplecov/rcov.

I can understand the suggestion for minitest, but simlecov/rcov are
coverage tools. What in simplecov/rcov do you have in mind that would
help with determinining test results?

-- 
milki

[toc] | [prev] | [next] | [standalone]

#3170

[Note:  parts of this message were removed to make it a legal post.]

>
>  What in simplecov/rcov do you have in mind that would

help with determinining test results?


Simplecov, at least in the way I'm using it, hooks into my existing rake
test task to do its thing with outputting coverage. That was the aspect I
was thinking of, latching onto another task.

[toc] | [prev] | [next] | [standalone]

#3126

[Note:  parts of this message were removed to make it a legal post.]

I guess you could simply analyze the output of a `rake test` task.

Maybe create a rake task that calls the :test task and processes its output?

-- 
Michael Sokol
On lundi 18 avril 2011 at 17:48, milki wrote: 
> Hi,
> 
> I'm building an integration tool between software projects and issue
> trackers. What would be the best way to report test success/failures
> from a ruby project?
> 
> I would need to be able to individually identify which tests
> failed, passed, or are pending (success on expected failures and fail if
> passing on an expected failure).
> I would also like to have minimal modifications if I wanted to add this
> tool to an existing ruby project.
> A report could either be written to a file or execute custom code to
> interact with another software package.
> 
> From what I have found, it would be best to hook into the rake system
> either via a custom runner or formatter. There isn't too much
> documentation on either of these so I'm not sure if this is the right
> way.
> 
> Any suggestions?
> 
> Thanks.
> milki
> 

[toc] | [prev] | [next] | [standalone]

#3167

On 09:05 Tue 19 Apr     , Michael Sokol wrote:
> I guess you could simply analyze the output of a `rake test` task.
> Maybe create a rake task that calls the :test task and processes its output?

I think this could work, but I'm not sure if it would destinguish
between pending test results or individual test results.

-- 
milki

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.ruby

csiph-web