Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

LINK TO THIS FORUM!

Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

Partner With Us!

"Best Of Breed" Forums Add Stickiness To Your Site
Partner Button
(Download This Button Today!)

Feedback

"...I have found your site brilliant. What makes it good are the people that contribute to the site..."

Geography

Where in the world do Tek-Tips members come from?

Need to run JUNIT code against a standalone service

DPlank (IS/IT--Management)
29 Jun 05 8:53
I have a service built by our development team.  They've tested it using JUNIT code, and started/stopped the server for each test they want to run.

This isn't appropriate for the testing I want to do.

Can anyone explain if it's possible for me to run the service outside of WSAD and still use the JUNIT code they've developed?

Or do I have to create an application to pass my parameters to the service?

Thanks in advance

Cheers,
Dave

Probably the only Test Analyst Manager on Tek-Tips...therefore whatever it was that went wrong, I'm to blame...

animadverto vos in Abyssus!

Take a look at forum1393!

gamerland (Programmer)
6 Jul 05 11:38
It is possible, and we do it all the time. Unless, you have very specific cache type testing needed.  In that case you may need to restart the server to have the data in cache reloaded.


The developers should create a junit test page for each service.  On that page put the input fields and a javascript to call and format the response.  Then have a "master" test index page so QA can get to each test.   

It takes a few minutes if you do it when you are developing the service and we require it for new services to make QA easier.  In addition, they should include every input field on the form. Even if it should be blank, empty, etc.  QA needs to test for the unexpected so they should not limit your options.  We give these a green background - but come up with your own scheme for required(white), optional(pale yellow), unentered(green).

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Back To Forum

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close