• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Pragmatic unittestingwithj unit
 

Pragmatic unittestingwithj unit

on

  • 836 views

JUnit tips and tricks

JUnit tips and tricks

Statistics

Views

Total Views
836
Views on SlideShare
522
Embed Views
314

Actions

Likes
1
Downloads
0
Comments
0

16 Embeds 314

http://liminescence.blogspot.com 286
http://liminescence.blogspot.co.uk 7
http://liminescence.blogspot.ca 6
http://liminescence.blogspot.in 3
http://www.blogger.com 1
http://liminescence.blogspot.com.br 1
http://www.slashdocs.com 1
http://liminescence.blogspot.com.es 1
http://liminescence.blogspot.nl 1
http://liminescence.blogspot.fr 1
http://liminescence.blogspot.kr 1
http://liminescence.blogspot.ru 1
http://liminescence.blogspot.de 1
http://liminescence.blogspot.ie 1
http://liminescence.blogspot.jp 1
http://liminescence.blogspot.co.nz 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • You are testing use cases – what should your class be doing
  • The constructor should have parameters similar to the what the data() method is returning.
  • Something that happens after a test is completed, like an assertInject behaviour to make JUnit add checks after each test…. kind of like a test post-condition or invariant from Betrand Meyers OO Software construction, but just for the tests themselvesVerifier is a base class for Rules like ErrorCollector, which can turn otherwise passing test methods into failing tests if a verification check is failed
  • Called when a test fails or succeeds.  Additional logging perhaps?  How about restarting a GUI, or take a screenshot when a test fails.
  • Called when a test fails or succeeds.  Additional logging perhaps?  How about restarting a GUI, or take a screenshot when a test fails.
  • Requires Eclipse 3.5+
  • Requires Eclipse 3.5+
  • methods 4 true

Pragmatic unittestingwithj unit Pragmatic unittestingwithj unit Presentation Transcript