The Artima Developer Community
Sponsored Link

SuiteRunner Forum
Suites for Suites

5 replies on 1 page. Most recent reply: Apr 7, 2003 3:55 AM by Adam Duffy

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 5 replies on 1 page
Adam Duffy

Posts: 168
Nickname: adamduffy
Registered: Feb, 2003

Suites for Suites Posted: Apr 3, 2003 2:38 AM
Reply to this message Reply
Advertisement
Hi,

I'm attempting to extend SuiteRunner for my own purposes. In doing so, I've refactored the Runner class and wanted to make sure that in doing so I have not omitted/broken any existing functionality. This leads me to my question.

In the suiterunner-1.0beta6-src.zip file contained in the Beta6 distribution, there is a directory called tests. Are these ALL the tests that were used in the development of SuiteRunner or are there others not included in the distribution?

Also, is the suiterunner-1.0beta6-src.zip file the actual development tree or has it been sanitised in some way?

Thanks,
Adam


Adam Duffy

Posts: 168
Nickname: adamduffy
Registered: Feb, 2003

Re: Suites for Suites Posted: Apr 3, 2003 2:43 AM
Reply to this message Reply
While I think of it, the recipe file for the tests included in the distribution mentioned above is as follows:


org.suiterunner.Suites=-s org.suiterunner.ctk.SuiteRunnerCTK -s org.suiterunner.ReportHolderSuite
org.suiterunner.Runpath=-p "."
org.suiterunner.Reporters=-o -r org.suiterunner.ctk.FunkyReporter


This runs all the tests that I found included in the source.
You may need to change the runpath as appropriate.

Adam

Bill Venners

Posts: 2284
Nickname: bv
Registered: Jan, 2002

Re: Suites for Suites Posted: Apr 3, 2003 4:17 PM
Reply to this message Reply
Embarassingly, I think those are all the tests. We didn't write our tests first. Every time we decided we'd have a test fest and write tests after the fact, we ended up doing new funcionality instead. My main reason for writing tests first, when I do it, is to make sure I do it. The same reason I try to exercise first thing in the morning. If I don't do it first, I often haven't done it yet.

Bill Venners

Posts: 2284
Nickname: bv
Registered: Jan, 2002

Re: Suites for Suites Posted: Apr 3, 2003 4:20 PM
Reply to this message Reply
> Also, is the suiterunner-1.0beta6-src.zip file the actual
> development tree or has it been sanitised in some way?
>
No, we do not practice sanitation. Is it possible for you to check things out directly from CVS at sourceforge? We may have to give people permission to do that at sourceforge. I don't know. Regardless, what you get in the zip file comes right out of the CVS sandbox for the project.

Bill Venners

Posts: 2284
Nickname: bv
Registered: Jan, 2002

Re: Suites for Suites Posted: Apr 3, 2003 4:27 PM
Reply to this message Reply
> I'm attempting to extend SuiteRunner for my own purposes.
> In doing so, I've refactored the Runner class and wanted
> to make sure that in doing so I have not omitted/broken
> any existing functionality. This leads me to my question.
>
I'm curious what your own purposes are. Any chance you could share with us what you're planning to do? We also have several enhancements in the works. I'm curious if there will be overlap.

Here are the main things we have planned in upcoming releases of SuiteRunner:

- ability to invoke and therefore test private and package access methods or public methods of innaccessible nested classes.
- ability to specify user-defined properties in the recipe file (we're calling that Spice), and passing a Map of context name-value pairs in the Reporter. This is how we plan to enable users to pass context to tests.
- making a few adjustments to facilitate testing distributed systems, including servlets, JSPs, EJBs, Jini systems, etc... Primarily, I'm considering changing the Thread in Report to a String threadName. This facilitates sending Reports between VMs without too much loss in the single-VM scenario.
- fixing a few bugs
- write more tests! We really need to have a test fest.

Adam Duffy

Posts: 168
Nickname: adamduffy
Registered: Feb, 2003

Re: Suites for Suites Posted: Apr 7, 2003 3:55 AM
Reply to this message Reply
To recap, there are 3 points for me to respond to here.

1. More tests.
2. Sanitation.
3. Enhancements.

As for point 1, I'm more than happy to help out with the test fest.

Point 2, the reason I asked about sanitation was that when downloading from the link off Artima site (as opposed to directly from CVS) the downloaded zip file does not contain the ant build.xml file. At present, the source zip file contained within the downloaded zip file only contains the contents of the source directory in the development tree. Perhaps the source zip file should be a zip of the development tree exactly as you would get from checking it out of CVS (minus the CVS directories and files)? How about I send you a slightly adjusted build file so that you can get an idea of what I'm saying. It's more a matter of personal preference than anything else. :)

As for point 3, I'm still in the process of designing my extension and have not fully worked it out yet. It does not in any way overlap on your future enhancements. It may be a few weeks before I have anything working. If and when I do, I'll send it to you and provide it on an open source license basis so you can review it (comments will be most welcome) and do whatever you or anyone else wishes to it.

Adam

Flat View: This topic has 5 replies on 1 page
Topic: Invoker Previous Topic   Next Topic Topic: org.suitrunner package

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use