The online community for software testing & quality assurance professionals
 
 
Calendar   Today's Topics
Sponsors:




Lost Password?

Home
BetaSoft
Blogs
Jobs
Training
News
Links
Downloads



Software Testing >> Unit Testing

Pages: 1
guylenee
Newbie


Reged: 08/31/10
Posts: 4
Document
      #640632 - 08/31/10 10:57 AM

Hi !

We have a serious problem here where the developer release their code without testing it ! It's a ping-pong game where we start testing it, send it back, receive it, etc.

Now, we think to ask unit test from developer. Without having to buy a product to register the unit test, I think to define a document.

Is there anybody that use unit test document ? Or do you have a better suggestion ?

Thank you !
-G


Post Extras: Print Post   Remind Me!   Notify Moderator  
TnkerBell
Active Member


Reged: 09/01/08
Posts: 1051
Loc: Neverland
Re: Document [Re: guylenee]
      #640846 - 09/02/10 01:49 AM

if you have a system test case template defined in your company, the same format / template can be used for recording uni test cases also.

--------------------
Regards,
Tinker

"The most wasted of all days is one without laughter."
-e e cummings


Post Extras: Print Post   Remind Me!   Notify Moderator  
guylenee
Newbie


Reged: 08/31/10
Posts: 4
Re: Document [Re: TnkerBell]
      #641035 - 09/03/10 05:47 AM

Hi !

No, we don't have particular template and testcase that is written doesn't value a lot !

The Unit test will be for developer where they sign it and give it to QA. This way, we will be sure that developer test before delivering their "new feature" !

Thank you !
-G


Post Extras: Print Post   Remind Me!   Notify Moderator  
Joe Strazzere
Moderator


Reged: 05/15/00
Posts: 12344
Loc: Massachusetts, USA
Re: Document [Re: guylenee]
      #641044 - 09/03/10 06:33 AM

It sounds like you only need something like this:


I, the undersigned have unit tested feature _______________


______________________
(developer's name)


______________________
(date)

--------------------
- Joe
Visit AllThingsQuality.com to learn more about quality, testing, and QA!

I speak only for me. I do not speak for my employer, nor for anyone else.


Post Extras: Print Post   Remind Me!   Notify Moderator  
guylenee
Newbie


Reged: 08/31/10
Posts: 4
Re: Document [Re: Joe Strazzere]
      #641081 - 09/03/10 09:28 AM

Yes but I think it will be better to have more meal. Like the way they test it !

Post Extras: Print Post   Remind Me!   Notify Moderator  
Joe Strazzere
Moderator


Reged: 05/15/00
Posts: 12344
Loc: Massachusetts, USA
Re: Document [Re: guylenee]
      #641089 - 09/03/10 10:06 AM

I'm not sure I understand.

Perhaps you could give us an example or two of what the developer would write that would explain "the way they test it"?

--------------------
- Joe
Visit AllThingsQuality.com to learn more about quality, testing, and QA!

I speak only for me. I do not speak for my employer, nor for anyone else.


Post Extras: Print Post   Remind Me!   Notify Moderator  
guylenee
Newbie


Reged: 08/31/10
Posts: 4
Re: Document [Re: Joe Strazzere]
      #641106 - 09/03/10 11:32 AM

Description of the new feature and how it works.

Maybe the code ?!? Define the extreme case. Define the way they test it with value ?!?


Post Extras: Print Post   Remind Me!   Notify Moderator  
JCTreb
Active Member


Reged: 08/16/01
Posts: 789
Loc: Minneapolis, MN
Re: Document [Re: guylenee]
      #641108 - 09/03/10 12:17 PM

Y'know, I'm not so sure a document is the solution to the problem. How easy is it to pencil-whip a document stating that unit testing is complete? Pretty easy, if you ask me. And not terribly meaningful to begin with. It feels like the document could end up pulling teams apart with finger-pointing due to defects that may find their way into a build for testing despite something in the way of a document that says unit testing was done. That'd be bad, mmmkay?

What you really need is a set of automated unit tests and reports from those unit tests indicating success/failure relative to the code being delivered. Beyond that, a set of automated tests for build acceptance would be good idea as well.

Bottom line: A document isn't a guarantee of quality. Effort put forth by the development/testing teams is a step in the right direction towards ensuring quality.

--------------------
Jason Trebilcock

"The single biggest problem in communication is the illusion that it has taken place."

-George Bernard Shaw, Irish playwright and Nobel Prize winner, 1856-1950


Post Extras: Print Post   Remind Me!   Notify Moderator  
Joe Strazzere
Moderator


Reged: 05/15/00
Posts: 12344
Loc: Massachusetts, USA
Re: Document [Re: guylenee]
      #641109 - 09/03/10 12:28 PM

Quote:

Description of the new feature and how it works.

Maybe the code ?!? Define the extreme case. Define the way they test it with value ?!?




(shrug) This all seems odd to me, but if it works in your shop, more power to you.

If it were me, I'd want to understand what you mean by "define extreme case" and "test it with value". Be prepared to teach people what you really want.

You may wish to chat with the Dev team and get their input before mandating your requirements and creating such a form.

Some folks rely on checkin comments within their source control system for some of this.

And some folks rely on Smoke Tests, and the resulting embarrassment when a developer has checked in code that breaks the Smoke Test, to heighten awareness of the need for (better) Unit Testing. In that regard, here are some motivational tools I've used in the past:
http://strazzere.blogspot.com/2010/04/dont-break-build.html

--------------------
- Joe
Visit AllThingsQuality.com to learn more about quality, testing, and QA!

I speak only for me. I do not speak for my employer, nor for anyone else.


Post Extras: Print Post   Remind Me!   Notify Moderator  
eyp
Newbie


Reged: 03/16/11
Posts: 3
Re: Document [Re: Joe Strazzere]
      #664556 - 03/16/11 10:23 AM

Hello, we have a similar problem. We have JUnit tests, but auditors ask us for evidences about them...

What must we do?. Which kind of report or document is recommended for automated tests?


Post Extras: Print Post   Remind Me!   Notify Moderator  
AnandTambey
Advanced Member


Reged: 11/11/07
Posts: 647
Loc: India
Re: Document [Re: eyp]
      #664638 - 03/17/11 12:26 AM

@eyp : - You can save/ask log files for evidence of unit tests by JMeter.

@guylenee:- Probably it is too much to ask from developers when the info about feature might be in requirement/design/wire frames(if available).

Getting back to real problem it seems that unit testing not been done.So you need to ask them for unit test case document/test logs i.e. status of test cases pass/fail. OR any automated unit tests/profiling result.


To enforce same you could have this fact in your test strategy entry criteria for starting testing.

# Unit test cases & Unit testing results(manual/automated) are available.


--------------------
Kind regards,
Anand Tambey

RSS Feed : Break To Make it Better
A Lazy person could be the best automation professional, if he is not lazy in implementing his ideas to reduce his work. ~Anand Tambey


Post Extras: Print Post   Remind Me!   Notify Moderator  
eyp
Newbie


Reged: 03/16/11
Posts: 3
Re: Document [Re: AnandTambey]
      #664650 - 03/17/11 01:49 AM

Quote:

@eyp : - You can save/ask log files for evidence of unit tests by JMeter.




Well, we aren't using JMeter, only JUnit, but logs have few details. i.g.:

This is the output of some tests that passed ok:

-------------------------------------------------------------------------------
Test set: es.rbcdexia.security.server.controllers.UserTest
-------------------------------------------------------------------------------
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.394 sec

What I was talking about is about documenting those tests. What people is used to do? How people document JUnit tests so they can give documentation to third people?


Post Extras: Print Post   Remind Me!   Notify Moderator  
AnandTambey
Advanced Member


Reged: 11/11/07
Posts: 647
Loc: India
Re: Document [Re: eyp]
      #664698 - 03/17/11 04:48 AM

Typically you can document with printing expected/actual values and verification messages.

Further to enhance/reuse it you may need to override watchmen class OR writing your own custom reporting class.


Post Extras: Print Post   Remind Me!   Notify Moderator  
Pages: 1



Extra information
0 registered and 2 anonymous users are browsing this forum.

Moderator:  AJ, Jeanj 

Print Topic

Forum Permissions
      You cannot start new topics
      You cannot reply to topics
      HTML is disabled
      UBBCode is enabled

Rating:
Topic views: 6424

Rate this topic

Jump to

Contact Us | Privacy statement SQAForums

Powered by UBB.threads™ 6.5.5