gmane.comp.java.junit.user archive

413 archived articles, newest first (page 2 of 5). Latest articles →

Re: Using MockitoJUnitRunner.class instead of SpringJUnit4ClassRunner.class
09 Jul 2015 12:03:13 -0700
"[email protected] [junit]" <[email protected]> • #20228
Using MockitoJUnitRunner.class instead of SpringJUnit4ClassRunner.class
28 Jun 2015 08:19:10 -0700
"[email protected] [junit]" <[email protected]> • #20227
Re: Informative equals
Thu, 2 Jul 2015 08:43:56 +0200
"Stefan Birkner [email protected] [junit]" <[email protected]> • #20226
Re: Informative equals
Wed, 1 Jul 2015 08:59:01 +0200
"Matthew Farwell [email protected] [junit]" <[email protected]> • #20225
Re: junit 4 - generating a test suite at runtime for each pair of tests.
Tue, 30 Jun 2015 01:36:10 -0700
"Kevin Cooney ☕ [email protected] [junit]" <[email protected]> • #20224
Re: junit 4 - generating a test suite at runtime for each pair of tests.
Mon, 29 Jun 2015 23:34:41 -0700
"Ray Tayek [email protected] [junit]" <[email protected]> • #20223
Re: Informative equals
Mon, 29 Jun 2015 11:55:30 +0100
"Colin Vipurs [email protected] [junit]" <[email protected]> • #20222
Re: Informative equals
Mon, 29 Jun 2015 12:44:34 +0200
"Johannes [email protected] [junit]" <[email protected]> • #20221
Using MockitoJUnitRunner.class instead of SpringJUnit4ClassRunner.class
Sun, 28 Jun 2015 21:28:13 +0530
"Ayaskant Swain [email protected] [junit]" <[email protected]> • #20220
Informative equals
26 Jun 2015 09:09:52 -0700
"[email protected] [junit]" <[email protected]> • #20219
Re: junit 4 - generating a test suite at runtime for each pair of tests.
Wed, 24 Jun 2015 09:56:58 -0400
"David Saff [email protected] [junit]" <[email protected]> • #20218
Re: junit 4 - generating a test suite at runtime for each pair of tests.
Tue, 23 Jun 2015 16:45:45 -0700
"Ray Tayek [email protected] [junit]" <[email protected]> • #20217
Re: junit 4 - generating a test suite at runtime for each pair of tests.
Tue, 23 Jun 2015 05:47:35 -0700
"Kevin Cooney ☕ [email protected] [junit]" <[email protected]> • #20216
Re: junit 4 - generating a test suite at runtime for each pair of tests.
Tue, 23 Jun 2015 20:44:25 +1000
"Paul King [email protected] [junit]" <[email protected]> • #20215
Re: junit 4 - generating a test suite at runtime for each pair of tests.
Tue, 23 Jun 2015 10:07:09 +0100
"Colin Vipurs [email protected] [junit]" <[email protected]> • #20214
junit 4 - generating a test suite at runtime for each pair of tests.
Mon, 22 Jun 2015 18:49:09 -0700
"Ray Tayek [email protected] [junit]" <[email protected]> • #20213
Re: Possibility to log ignored tests
12 Jun 2015 09:01:53 -0700
"[email protected] [junit]" <[email protected]> • #20212
Re: Proposal for Assert.assertException
04 Jun 2015 06:05:37 -0700
"[email protected] [junit]" <[email protected]> • #20211
Re: Custom classloader
Tue, 19 May 2015 21:17:48 -0700
"Bill Shannon [email protected] [junit]" <[email protected]> • #20210
Re: Custom classloader
Tue, 19 May 2015 14:37:28 -0700
"Johannes Ernst [email protected] [junit]" <[email protected]> • #20209
Re: Custom classloader
Tue, 19 May 2015 14:36:12 -0700
"Johannes Ernst [email protected] [junit]" <[email protected]> • #20208
Re: Custom classloader
Tue, 19 May 2015 13:53:13 -0700
"Bill Shannon [email protected] [junit]" <[email protected]> • #20207
Re: Custom classloader
Tue, 19 May 2015 14:01:10 -0400
"David Saff [email protected] [junit]" <[email protected]> • #20206
Re: Proposal for Assert.assertException
Tue, 19 May 2015 13:57:40 -0400
"David Saff [email protected] [junit]" <[email protected]> • #20205
Proposal for Assert.assertException
Tue, 19 May 2015 07:06:08 +0200
"Johannes [email protected] [junit]" <[email protected]> • #20204
Re: Custom classloader
Tue, 19 May 2015 13:11:04 +0200
"Malte Finsterwalder [email protected] [junit]" <[email protected]> • #20203
Re: Custom classloader
Tue, 19 May 2015 08:56:06 +0200
"Dawid Weiss [email protected] [junit]" <[email protected]> • #20202
Re: Custom classloader
Mon, 18 May 2015 13:55:38 -0700
"Johannes Ernst [email protected] [junit]" <[email protected]> • #20201
Re: Custom classloader
Sun, 17 May 2015 23:59:42 -0700
"Aaron VonderHaar [email protected] [junit]" <[email protected]> • #20200
Re: assertEquals fails to assert for arrays of primary data type
Sun, 17 May 2015 18:28:33 -0400
"Corey Vaillancourt [email protected] [junit]" <[email protected]> • #20199
assertEquals fails to assert for arrays of primary data type
Sun, 17 May 2015 22:00:03 +0800
"XueFeng [email protected] [junit]" <[email protected]> • #20198
Custom classloader
14 May 2015 17:34:18 -0700
"[email protected] [junit]" <[email protected]> • #20197
Re: Possibility to log ignored tests
Wed, 11 Mar 2015 18:57:14 +0300
"Nikita Merinov [email protected] [junit]" <[email protected]> • #20196
Re: Possibility to log ignored tests
Wed, 11 Mar 2015 10:25:30 -0400
"David Saff [email protected] [junit]" <[email protected]> • #20195
Re: Possibility to log ignored tests
Tue, 10 Mar 2015 19:12:08 +0300
"Nikita Merinov [email protected] [junit]" <[email protected]> • #20194
Re: Possibility to log ignored tests
Mon, 9 Mar 2015 15:36:52 -0400
"David Saff [email protected] [junit]" <[email protected]> • #20193
Re:
Sun, 8 Mar 2015 18:24:37 -0700 (PDT)
"[email protected] [junit]" <[email protected]> • #20192
Possibility to log ignored tests
Mon, 9 Mar 2015 02:06:29 +0300
"Nikita Merinov [email protected] [junit]" <[email protected]> • #20191
Re: a few feature and many fixtures
Sat, 28 Feb 2015 03:23:52 -0800
"Ray Tayek [email protected] [junit]" <[email protected]> • #20190
Re: a few feature and many fixtures
Mon, 23 Feb 2015 17:01:09 -0800
"Ray Tayek [email protected] [junit]" <[email protected]> • #20189
Re: a few feature and many fixtures
Mon, 23 Feb 2015 16:03:08 -0500
"David Saff [email protected] [junit]" <[email protected]> • #20188
4-Minute Video
23 Feb 2015 04:15:37 -0800
"[email protected] [junit]" <[email protected]> • #20187
a few feature and many fixtures
21 Feb 2015 19:17:04 -0800
"[email protected] [junit]" <[email protected]> • #20186
Re: Is tests.jvms calculated by junit, ant, or the ant config?
11 Feb 2015 15:09:07 -0800
"[email protected] [junit]" <[email protected]> • #20185
Re: Is tests.jvms calculated by junit, ant, or the ant config?
Wed, 11 Feb 2015 21:19:27 +0100
"Dawid Weiss [email protected] [junit]" <[email protected]> • #20184
Re: Is tests.jvms calculated by junit, ant, or the ant config?
Wed, 11 Feb 2015 15:18:39 -0500
"David Saff [email protected] [junit]" <[email protected]> • #20183
Is tests.jvms calculated by junit, ant, or the ant config?
11 Feb 2015 12:01:47 -0800
"[email protected] [junit]" <[email protected]> • #20182
Tests4j
Mon, 12 Jan 2015 18:30:41 -0600
"Scott Morgan [email protected] [junit]" <[email protected]> • #20181
Re: Decoupling JUnit and Hamcrest
12 Jan 2015 15:20:54 -0800
"[email protected] [junit]" <[email protected]> • #20180
Re: Decoupling JUnit and Hamcrest
Mon, 12 Jan 2015 21:51:02 +0100
"Stefan [email protected] [junit]" <[email protected]> • #20179
Re: Decoupling JUnit and Hamcrest
Mon, 12 Jan 2015 18:26:36 +0200
"Esko Luontola [email protected] [junit]" <[email protected]> • #20178
Re: Decoupling JUnit and Hamcrest
Mon, 12 Jan 2015 12:53:34 +0100
"Stefan Bechtold [email protected] [junit]" <[email protected]> • #20177
Re: Decoupling JUnit and Hamcrest
11 Jan 2015 11:27:12 -0800
"[email protected] [junit]" <[email protected]> • #20176
Re: Decoupling JUnit and Hamcrest
Sun, 11 Jan 2015 20:21:48 +0000
"Stephen Connolly [email protected] [junit]" <[email protected]> • #20175
Re: Decoupling JUnit and Hamcrest
Sun, 11 Jan 2015 18:04:44 +0100
"Stefan Bechtold [email protected] [junit]" <[email protected]> • #20174
Re: Decoupling JUnit and Hamcrest
Thu, 8 Jan 2015 23:15:34 +0100
"Stefan Birkner [email protected] [junit]" <[email protected]> • #20173
Re: Decoupling JUnit and Hamcrest
Thu, 08 Jan 2015 21:46:24 +0100
"Stefan [email protected] [junit]" <[email protected]> • #20172
Decoupling JUnit and Hamcrest
Wed, 7 Jan 2015 08:31:55 +0100
"Stefan Birkner [email protected] [junit]" <[email protected]> • #20171
Re: How to reliable identify Failure caused by @BeforeClass?
Tue, 16 Dec 2014 10:09:51 -0500
"David Saff [email protected] [junit]" <[email protected]> • #20170
Re: How to reliable identify Failure caused by @BeforeClass?
Tue, 16 Dec 2014 07:28:16 +0000
"Chris [email protected] [junit]" <[email protected]> • #20169
Re: How to reliable identify Failure caused by @BeforeClass?
Mon, 15 Dec 2014 11:45:30 -0500
"David Saff [email protected] [junit]" <[email protected]> • #20168
How to reliable identify Failure caused by @BeforeClass?
Mon, 15 Dec 2014 12:11:26 +0000
"Chris [email protected] [junit]" <[email protected]> • #20167
JUnit 4.12 is released!
04 Dec 2014 11:37:43 -0800
"[email protected] [junit]" <[email protected]> • #20166
Re: passing arguments to test case while adding them to test suite
Thu, 27 Nov 2014 19:55:05 -0500
"David Saff [email protected] [junit]" <[email protected]> • #20165
Re: passing arguments to test case while adding them to test suite
Tue, 25 Nov 2014 09:09:53 +0000 (UTC)
"ishan gupta [email protected] [junit]" <[email protected]> • #20164
Re: passing arguments to test case while adding them to test suite
Tue, 25 Nov 2014 09:11:26 +0000 (UTC)
"ishan gupta [email protected] [junit]" <[email protected]> • #20163
Re: passing arguments to test case while adding them to test suite
Tue, 25 Nov 2014 07:11:40 +0100
"Stefan Bechtold [email protected] [junit]" <[email protected]> • #20162
Re: passing arguments to test case while adding them to test suite
Tue, 25 Nov 2014 01:19:18 +0530
"Manan Patel [email protected] [junit]" <[email protected]> • #20161
Re: passing arguments to test case while adding them to test suite
Mon, 24 Nov 2014 12:03:21 -0500
"David Saff [email protected] [junit]" <[email protected]> • #20160
passing arguments to test case while adding them to test suite
23 Nov 2014 20:59:11 -0800
"[email protected] [junit]" <[email protected]> • #20159
JUnit 4.12-beta-3 is released
09 Nov 2014 10:51:06 -0800
"[email protected] [junit]" <[email protected]> • #20158
Re: Junit4 -Backward compatibility
Sat, 8 Nov 2014 06:20:41 +0000
Sajeev Vela <[email protected]> • #20157
Re: [Junit-devel] Junit4 -Backward compatibility
Fri, 7 Nov 2014 09:56:35 -0500
"David Saff [email protected] [junit]" <[email protected]> • #20156
Re: Quo Vadis JUnit
Thu, 23 Oct 2014 21:59:22 -0400
"David Saff [email protected] [junit]" <[email protected]> • #20155
Re: Quo Vadis JUnit
Thu, 23 Oct 2014 20:40:44 -0400
"David Saff [email protected] [junit]" <[email protected]> • #20154
Re: Quo Vadis JUnit
Thu, 23 Oct 2014 23:12:52 +0200
"Stefan Bechtold [email protected] [junit]" <[email protected]> • #20153
Re: Quo Vadis JUnit
Thu, 23 Oct 2014 20:45:16 +0300
"Esko Luontola [email protected] [junit]" <[email protected]> • #20152
Re: Quo Vadis JUnit
Thu, 23 Oct 2014 10:25:24 -0400
"David Saff [email protected] [junit]" <[email protected]> • #20151
Quo Vadis JUnit
22 Oct 2014 22:10:02 -0700
"[email protected] [junit]" <[email protected]> • #20150
Re: JUnit extended class category
Wed, 22 Oct 2014 16:33:46 -0400
"David Saff [email protected] [junit]" <[email protected]> • #20149
JUnit extended class category
21 Oct 2014 15:45:54 -0700
"[email protected] [junit]" <[email protected]> • #20148
Re: JUnit shouldn't be advertised as only for "unit testing"
Mon, 6 Oct 2014 15:57:36 -0700
"Cédric Beust ♔ [email protected] [junit]" <[email protected]> • #20147
Re: JUnit shouldn't be advertised as only for "unit testing"
Mon, 6 Oct 2014 21:45:31 +0100
"Stephen Connolly [email protected] [junit]" <[email protected]> • #20146
RE: JUnit shouldn't be advertised as only for "unit testing"
Mon, 6 Oct 2014 20:22:36 +0000
"'KARR, DAVID' [email protected] [junit]" <[email protected]> • #20145
Re: JUnit shouldn't be advertised as only for "unit testing"
Mon, 6 Oct 2014 20:27:43 +0100
"Stephen Connolly [email protected] [junit]" <[email protected]> • #20144
JUnit shouldn't be advertised as only for "unit testing"
Mon, 6 Oct 2014 18:25:56 +0000
"'KARR, DAVID' [email protected] [junit]" <[email protected]> • #20143
JUnit 4.12-beta-2 is released
25 Sep 2014 07:39:33 -0700
"[email protected] [junit]" <[email protected]> • #20142
Re: JUnit compatibility (was: Re: Re: JUnit 4.12-beta-1 is released)
22 Sep 2014 11:00:46 -0700
"[email protected] [junit]" <[email protected]> • #20141
Re:
Mon, 22 Sep 2014 07:40:14 -0700 (PDT)
"[email protected] [junit]" <[email protected]> • #20140
Re: JUnit compatibility (was: Re: Re: JUnit 4.12-beta-1 is released)
Mon, 22 Sep 2014 13:43:26 +0100
"Chris [email protected] [junit]" <[email protected]> • #20139
Re: JUnit compatibility (was: Re: Re: JUnit 4.12-beta-1 is released)
Wed, 13 Aug 2014 09:25:34 -0700
"Kevin Cooney [email protected] [junit]" <[email protected]> • #20138
JUnit compatibility (was: Re: Re: JUnit 4.12-beta-1 is released)
Wed, 13 Aug 2014 11:37:59 -0400
"David Saff [email protected] [junit]" <[email protected]> • #20137
Re: Re: JUnit 4.12-beta-1 is released
Wed, 13 Aug 2014 07:42:40 +0100
"Chris [email protected] [junit]" <[email protected]> • #20136
Re: Re: JUnit 4.12-beta-1 is released
Tue, 12 Aug 2014 23:18:11 +0200
"Stefan [email protected] [junit]" <[email protected]> • #20135
Re: Re: JUnit 4.12-beta-1 is released
Tue, 12 Aug 2014 12:32:24 -0700
"Kevin Cooney [email protected] [junit]" <[email protected]> • #20134
Re: Re: JUnit 4.12-beta-1 is released
Tue, 12 Aug 2014 12:08:09 -0700
"Kevin Cooney [email protected] [junit]" <[email protected]> • #20133
Re: Re: JUnit 4.12-beta-1 is released
Tue, 12 Aug 2014 15:06:45 -0400
"David Saff [email protected] [junit]" <[email protected]> • #20132
Re: JUnit 4.12-beta-1 is released
12 Aug 2014 10:53:58 -0700
"[email protected] [junit]" <[email protected]> • #20131
Re: Re: JUnit 4.12-beta-1 is released
Tue, 12 Aug 2014 07:28:18 +0100
"Chris [email protected] [junit]" <[email protected]> • #20130
Re: semantic versioning & backward compatibility
Mon, 11 Aug 2014 21:49:34 +0200
"Stefan Birkner [email protected] [junit]" <[email protected]> • #20129
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.