junit

问题 I have several different test classes that require that certain objects are created before those tests can be run. Now I'm wondering if I should put the object initialization code into a separate helper class or superclass. Doing so would surely reduce the amount of duplicate code in my test classes but it would also make them less readable. Is there a guideline or pattern how to deal with common setUp-code for unit tests? 回答1: Patterns and practices when dealing with test code is no

问题 I would like to know if I can mock a super class constructors call and its super() calls. For example, I have the following classes class A { A(..) { super(..) } } class B extends A { B(C c) { super(c) } } So, I am planning to unit test some methods in class B, but when creating an instance it does call the super class constructors making it tough to write unit tests. So, how can I mock all the super class constructor calls. Also I would like to mock few methods in class A so that it does

问题 I am using the Maven Surefire plugin in order to run just a specific suite of tests. For instance: package suite; import org.junit.runner.RunWith; import org.junit.runners.Suite; import suite.slow.EvenSlowerClassTest; import suite.slow.SlowClassTest; @RunWith(Suite.class) @Suite.SuiteClasses({ SlowClassTest.class, EvenSlowerClassTest.class }) public class SlowSuite { } By using the maven command test -DrunSuite=**/FastSuite.class -DfailIfNoTests=false I can run the FastSuite or SlowSuite test

问题 This is strange: I am using JUnit with JMock using the Rule JUnitRuleMockery for a while and it always worked perfectly fine: expectations where checked at the end of the test and if one (or more) was missing the test was failing. However, this snippet is not working for me in Eclipse ( DAO is the interface described in org.mongodb.morphia.dao.DAO ): @Rule public JUnitRuleMockery context = new JUnitRuleMockery(); private DAO<Cobrand, ObjectId> dao = context.mock(DAO.class); private final

问题 So I'm attempting to run parallel parameterized tests. I have a solution where the same test can run in parallel with the parameters supplied for example say I have the following: @Test public void someTest1(){ } @Test public void someTest2(){ } I can get someTest1() to run with all the parameters concurrently, but someTest2() will have still have to wait for someTest1() to complete with all parameters before executing. I was wondering if anyone knew of a solution to be able to run someTest1(

问题 I developed some JUnit tests that extend org.apache.struts2.StrutsTestCase. I used the tutorial on struts.apache.org as my starting point. Everything was working fine until I modified my simple web application to use Tiles. I have Tiles working fine in the app but now my Action test cases have stopped working. I'm getting NullPointerException at org.apache.struts2.views.tiles.TilesResult.doExecute when I run the following line of code: ActionProxy proxy = getActionProxy("/displaytag.action");

问题 This seems like it shouldn't compile and run as Object does not have a fail() method. At compile time is something funky happening? (I am using NetBeans): import static org.junit.Assert.*; import org.junit.Test; public class Test { @Test public void hello() { fail(); } } Regards, Guido 回答1: Your import static line imports all static members of the Assert class into the static namespace of your compilation unit. The fail() call refers to Assert.fail() . The confusion you are experiencing

问题 A fairly normal scenario: an Android application has a preferences activity, and selecting an option from a ListPreference triggers code to change that ListPreference's summary text. ie: Selecting "Green" from a color ListPreference would change the ListPreference's summary text to "Green" through a onPreferenceChange callback. I'd like to be able to use the Android JUnit testing to confirm that these summary changes are all being performed correctly. However, there seems to be very little

问题 I have a set of scripts that produces a JUnit output for Jenkins. The code I execute looks like this (this is just a snippet so you get the idea) : #!/usr/bin/env perl use strict; use warnings; use Test::More; use TAP::Harness; use Test::Builder; my $runner = sub { my ($harness,$test) = @_; sleep(2); my $builder = Test::Builder->new; $builder->reset; $builder->output( \my ($out) ); $builder->failure_output( \$out ); $builder->todo_output( \$out ); $builder->is_eq($test,'test', 'Test is test')