HTML reporter for Test::Unit

Tesly Jr. (http://junior.tesly.com) is a hosted web app that provides
an HTML reporter for your unit tests. With an RSS feed that gets
updated with your test results every time you run your tests, it’s
great for continuous integration. The web interface to your test
results also helps to prove that you’re actually running tests. :slight_smile:

It’s free and easy. Set up an account, download and configure the
code that extends Test::Unit, and be amazed as lovely green bars show
up on the web as you run your tests.

AWESOME!

Will test this now.

I’d pay for something like this, if stable & always available.

It’s great, I tested it.

Very easy to setup, clean interface, awesome.

Notifying me by email if test cases fail would probably be the ontly
thing
that’s missing for some kind of CI.

Thanks,
Rob

This looks neat, but, will you ever be opening up the webapp source?

I may open the code at some point in the future, but not in the near
future.

Thanks for the feedback. I’ll take a look at adding email support.

On Oct 7, 2006, at 9:06 PM, Benjamin C. wrote:

Tesly Jr. (http://junior.tesly.com) is a hosted web app that
provides an HTML reporter for your unit tests. With an RSS feed
that gets updated with your test results every time you run your
tests, it’s great for continuous integration. The web interface to
your test results also helps to prove that you’re actually running
tests. :slight_smile:

It’s free and easy. Set up an account, download and configure the
code that extends Test::Unit, and be amazed as lovely green bars
show up on the web as you run your tests.

Hey Benjamin-

Very cool little app. Nice idea and good execution.

-Ezra

On Sun, 2006-10-08 at 13:06 +0900, Benjamin C. wrote:

Tesly Jr. (http://junior.tesly.com) is a hosted web app that provides
an HTML reporter for your unit tests.

Hmm, pretty cool idea, but it doesn’t seem to be picking up my test
runs. Is there a problem with that side of things at the moment?

I took a look in the logs and it looks like your test results were
never sent to the app. Are you sure you’re including
tesly_reporter.rb to get Test::Unit extended?

This is great. Easy to setup with my Rails tests.

Did run into a problem with the Ruby Test::Unit though. Seems as if
there
are Rails dependencies (see line below) that aren’t mentioned in the
setup
instructions. I might be missing something obvious though.

cattr_accessor :app_name, :user

Thanks for the excellent contribution.

tim

On 10/8/06, Tim K. [email protected] wrote:

This is great. Easy to setup with my Rails tests.

Did run into a problem with the Ruby Test::Unit though. Seems as if there
are Rails dependencies (see line below) that aren’t mentioned in the setup
instructions. I might be missing something obvious though.

cattr_accessor :app_name, :user

Thanks for the excellent contribution.

Is that ‘class attribute accessor’? If so, try just replacing it with

class << self; attr_accessor :app_name, :user; end

On Mon, 2006-10-09 at 12:31 +0900, Tim K. wrote:

This is great. Easy to setup with my Rails tests.

Did run into a problem with the Ruby Test::Unit though. Seems as if there
are Rails dependencies (see line below) that aren’t mentioned in the setup
instructions. I might be missing something obvious though.

cattr_accessor :app_name, :user

Ahh, I thought I’d added a typo when pasting in the app/user stuff off
the website, so I’d changed that (back, I thought) to attr_accessor. No
wonder it didn’t work.

I just had a bit of a play but still no joy, I’ll have to have another
look later because this does look pretty cool.

Yup, you weren’t missing something, I was. :slight_smile: The tesly_reporter.rb
has been updated to actually work, now. :slight_smile:

Thanks for the suggestion… I forgot to switch mental gears from
Rails to Ruby. :slight_smile: I ditched the class attributes in favor of plain
'ol constants.

There were a couple of problems on my part that was keeping it form
working. Download the revised tesly_reporter.rb and all should be
well. :slight_smile: Sorry for the inconvenience.

Hi –

On Mon, 9 Oct 2006, Gregory B. wrote:

Is that ‘class attribute accessor’? If so, try just replacing it with

class << self; attr_accessor :app_name, :user; end

If it’s the Rails cattr_accessor then it uses class variables rather
than instance variables. It wouldn’t be a bad idea to rewrite it to
use instance variables, though – or perhaps rename it – since class
variables are not object-specific and are therefore not really capable
of storing object “attributes”.

David

As requested, you can now choose to receive an email if a test run
doesn’t pass 100%. :slight_smile:


Building an e-commerce site with Rails?
http://www.agilewebdevelopment.com/rails-ecommerce

Yeah, that’s got it, And it is pretty cool, too :slight_smile:

Thanks,
Ross

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs