librelist archives

« back to archive

Testing Shoes4

Testing Shoes4

From:
Douglas Allen
Date:
2013-04-17 @ 20:47
Hey All,

   I'm trying to run some of the tests on shoes4 with rspec.
My console which is ansicon see:https://github.com/adoxa/ansicon
is not giving me any colors just escape values such as
←[32m1 example, 0 failures←[0m
I get colors with my Rails apps testing in ansicon.
Oh! I'm on windows XP, JRuby 1.7.3 from pik
I have --color in the .rspec file also.
Please tell me more about testing shoes in JRuby. I'm just learning
testing after all this time learning Ruby.
That's what sucks. Nobody teaches
it right until about three years ago?
I'm sorry Microsoft doesn't comply with C99 but that's not the users fault.
Maybe some day the source for Ruby will get written to compile in
the MS cl.exe
But what's that got to do with JRuby? I have a JVM installed.
Thanks while *I rant.*
*
*

Re: [shoes] Testing Shoes4

From:
Eric Watson
Date:
2013-04-22 @ 14:13
On Apr 17, 2013, at 3:47 PM, Douglas Allen <kb9agt@gmail.com> wrote:

> Please tell me more about testing shoes in JRuby.

I don't have Windows, so I can't speak about Windows-specifics, but here's
what I can tell you about the specs in Shoes4. They are designed to be run
from a Rake task (which is fine, but makes it difficult to run a single 
file--patches welcome!). You can get a list of the rake tasks as usual:

    rake -T

and there is a list in the README[1]. Specifically for Windows, it looks 
like you should run this command:

    C:\tmp\shoes4>jruby --1.9 -S rake spec

Hope that helps!

As a side note, I think this is a big issue, because it's a barrier for 
you becoming involved in developing Shoes. We need to remove all of those 
barriers...so I hope we can get your specs running! :)

Eric



[1] 
https://github.com/shoes/shoes4/tree/1e6eeb9031dfbf908eff4275ac88a0426d5b0360#running-specs

Re: [shoes] Testing Shoes4

From:
Douglas Allen
Date:
2013-04-23 @ 02:10
Thanks Eric.
Tests run okay but there is so much data coming back that I will have to
increase the buffer for the cmd shell or learn what the coverage report
does. There 's two pending and two failed tests show up at the end. Would
anyone like to see the report? Tell me what I need to do.
Thanks. "AMD Athlon on Old Compaq with Dell XP Windows OS"


On Mon, Apr 22, 2013 at 9:13 AM, Eric Watson <wasnotrice@gmail.com> wrote:

>
> On Apr 17, 2013, at 3:47 PM, Douglas Allen <kb9agt@gmail.com> wrote:
>
> > Please tell me more about testing shoes in JRuby.
>
> I don't have Windows, so I can't speak about Windows-specifics, but here's
> what I can tell you about the specs in Shoes4. They are designed to be run
> from a Rake task (which is fine, but makes it difficult to run a single
> file--patches welcome!). You can get a list of the rake tasks as usual:
>
>     rake -T
>
> and there is a list in the README[1]. Specifically for Windows, it looks
> like you should run this command:
>
>     C:\tmp\shoes4>jruby --1.9 -S rake spec
>
> Hope that helps!
>
> As a side note, I think this is a big issue, because it's a barrier for
> you becoming involved in developing Shoes. We need to remove all of those
> barriers...so I hope we can get your specs running! :)
>
> Eric
>
>
>
> [1]
> 
https://github.com/shoes/shoes4/tree/1e6eeb9031dfbf908eff4275ac88a0426d5b0360#running-specs
>

Re: [shoes] Testing Shoes4

From:
Eric Watson
Date:
2013-04-23 @ 02:57
On Apr 22, 2013, at 9:10 PM, Douglas Allen <kb9agt@gmail.com> wrote:

> Tests run okay but there is so much data coming back that I will have to
increase the buffer for the cmd shell or learn what the coverage report 
does. There 's two pending and two failed tests show up at the end. 

I just pushed a commit that makes rspec show dots for commits instead of 
so much text. If you pull the lastest from github, you should see results 
that are much less verbose, and easier to deal with. I have been meaning 
to do this for a while now--thanks for the impetus :)

The coverage report (I downloaded it fine) is just a metric describing 
what parts of the codebase are covered by specs. It shouldn't affect the 
spec run, in terms of failing specs.

I would be interested to see which specs are failing. I know about the two
pending specs, but we shouldn't have any failures...

Eric

Re: [shoes] Testing Shoes4

From:
Douglas Allen
Date:
2013-04-23 @ 04:20
here is some info
Rakefile:15: Use RbConfig instead of obsolete and deprecated Config.
mind you this is before I get the updated shoes4
Lots of warnings
here's the failures

  1) Shoes::Swt::Package::App when creating a .app makes launcher executable
     Failure/Error: launcher.should be_executable
       expected executable? to return true, got false
     # ./spec/swt_shoes/package_app_spec.rb:50:in `(root)'

  2) Shoes::Swt::Package::Jar when creating a .jar creates .jar smaller
than 51MB
     Failure/Error: File.size(output_file).should be < 51 * 1024 * 1024
       expected: < 53477376
            got:   54266544
     # ./spec/swt_shoes/package_jar_spec.rb:34:in `(root)'

Finished in 2 minutes 29.83 seconds
761 examples, 2 failures, 2 pending

Failed examples:

rspec ./spec/swt_shoes/package_app_spec.rb:49 # Shoes::Swt::Package::App
when creating a .app makes launcher executable
rspec ./spec/swt_shoes/package_jar_spec.rb:33 # Shoes::Swt::Package::Jar
when creating a .jar creates .jar smaller than 51MB
Other than that, yes the first half passes.


On Mon, Apr 22, 2013 at 9:57 PM, Eric Watson <wasnotrice@gmail.com> wrote:

>
> On Apr 22, 2013, at 9:10 PM, Douglas Allen <kb9agt@gmail.com> wrote:
>
> > Tests run okay but there is so much data coming back that I will have to
> increase the buffer for the cmd shell or learn what the coverage report
> does. There 's two pending and two failed tests show up at the end.
>
> I just pushed a commit that makes rspec show dots for commits instead of
> so much text. If you pull the lastest from github, you should see results
> that are much less verbose, and easier to deal with. I have been meaning to
> do this for a while now--thanks for the impetus :)
>
> The coverage report (I downloaded it fine) is just a metric describing
> what parts of the codebase are covered by specs. It shouldn't affect the
> spec run, in terms of failing specs.
>
> I would be interested to see which specs are failing. I know about the two
> pending specs, but we shouldn't have any failures...
>
> Eric
>

Re: [shoes] Testing Shoes4

From:
ashbb
Date:
2013-04-23 @ 22:28
Hi Douglas,

> this is before I get the updated shoes4
Ah,.. does this mean "after updating there is no failures"?

I'm using Windows 7 with jruby 1.7.3 (1.9.3p385). I have no failures for
the latest Shoes4 (commit a49f0e7031).

---------
Finished in 13.73 seconds
759 examples, 0 failures, 2 pending
---------

ashbb