6 | Developers love self-referential programs! Hence, NUnit has always run all it's 7 | own tests, even those that are not really unit tests. 8 |
Now, beginning with NUnit 2.4, NUnit has top-level tests using Ward Cunningham's 9 | FIT framework. At this time, the tests are pretty rudimentary, but it's a start 10 | and it's a framework for doing more. 11 |
Open a console or shell window and navigate to the NUnit bin directory, which 13 | contains this file. To run the test under Microsoft .Net, enter the command 14 |
runFile NUnitFitTests.html TestResults.html .15 | To run it under Mono, enter 16 |
mono runFile.exe NUnitFitTests.html TestResults.html .17 | Note the space and dot at the end of each command. The results of your test 18 | will be in TestResults.html in the same directory. 19 |
| NUnit.Fixtures.PlatformInfo | 23 |
27 | Load and run the NUnit unit tests, verifying that the results are as expected. 28 | When these tests are run on different platforms, different numbers of tests may 29 | be skipped, so the values for Skipped and Run tests are informational only. 30 |
31 | The number of tests in each assembly should be constant across all platforms - 32 | any discrepancy usually means that one of the test source files was not 33 | compiled on the platform. There should be no failures and no tests ignored. 34 |
Note: 35 | At the moment, the nunit.extensions.tests assembly is failing because the 36 | fixture doesn't initialize addins in the test domain. 37 |
38 |
| NUnit.Fixtures.AssemblyRunner | 41 ||||||
| Assembly | 44 |Tests() | 45 |Run() | 46 |Skipped() | 47 |Ignored() | 48 |Failures() | 49 |
| nunit.framework.tests.dll | 52 |397 | 53 |54 | | 55 | | 0 | 56 |0 | 57 |
| nunit.core.tests.dll | 60 |355 | 61 |62 | | 63 | | 0 | 64 |0 | 65 |
| nunit.util.tests.dll | 68 |238 | 69 |70 | | 71 | | 0 | 72 |0 | 73 |
| nunit.mocks.tests.dll | 76 |43 | 77 |78 | | 79 | | 0 | 80 |0 | 81 |
| nunit.extensions.tests.dll | 84 |5 | 85 |86 | | 87 | | 0 | 88 |0 | 89 |
| nunit-console.tests.dll | 92 |40 | 93 |94 | | 95 | | 0 | 96 |0 | 97 |
| nunit.uikit.tests.dll | 100 |34 | 101 |102 | | 103 | | 0 | 104 |0 | 105 |
| nunit-gui.tests.dll | 108 |15 | 109 |110 | | 111 | | 0 | 112 |0 | 113 |
| nunit.fixtures.tests.dll | 116 |6 | 117 |118 | | 119 | | 0 | 120 |0 | 121 |
125 | These tests create a test assembly from a snippet of code and then load and run 126 | the tests that it contains, verifying that the structure of the loaded tests is 127 | as expected and that the number of tests run, skipped, ignored or failed is 128 | correct. 129 |
130 |
| NUnit.Fixtures.SnippetRunner | 133 ||||||
| Code | 136 |Tree() | 137 |Run() | 138 |Skipped() | 139 |Ignored() | 140 |Failures() | 141 |
public class TestClass
144 | {
145 | }
146 | |
147 | EMPTY | 148 |0 | 149 |0 | 150 |0 | 151 |0 | 152 |
using NUnit.Framework;
155 |
156 | [TestFixture]
157 | public class TestClass
158 | {
159 | }
160 | |
161 | TestClass | 162 |0 | 163 |0 | 164 |0 | 165 |0 | 166 |
using NUnit.Framework;
169 |
170 | [TestFixture]
171 | public class TestClass
172 | {
173 | [Test]
174 | public void T1() { }
175 | [Test]
176 | public void T2() { }
177 | [Test]
178 | public void T3() { }
179 | }
180 | |
181 | TestClass 182 | >T1 183 | >T2 184 | >T3185 | |
186 | 3 | 187 |0 | 188 |0 | 189 |0 | 190 |
using NUnit.Framework;
193 |
194 | [TestFixture]
195 | public class TestClass1
196 | {
197 | [Test]
198 | public void T1() { }
199 | }
200 |
201 | [TestFixture]
202 | public class TestClass2
203 | {
204 | [Test]
205 | public void T2() { }
206 | [Test]
207 | public void T3() { }
208 | }
209 | |
210 | TestClass1 211 | >T1 212 | TestClass2 213 | >T2 214 | >T3215 | |
216 | 3 | 217 |0 | 218 |0 | 219 |0 | 220 |
using NUnit.Framework;
223 |
224 | [TestFixture]
225 | public class TestClass
226 | {
227 | [Test]
228 | public void T1() { }
229 | [Test, Ignore]
230 | public void T2() { }
231 | [Test]
232 | public void T3() { }
233 | }
234 | |
235 | TestClass 236 | >T1 237 | >T2 238 | >T3239 | |
240 | 2 | 241 |0 | 242 |1 | 243 |0 | 244 |
using NUnit.Framework;
247 |
248 | [TestFixture]
249 | public class TestClass
250 | {
251 | [Test]
252 | public void T1() { }
253 | [Test, Explicit]
254 | public void T2() { }
255 | [Test]
256 | public void T3() { }
257 | }
258 | |
259 | TestClass 260 | >T1 261 | >T2 262 | >T3263 | |
264 | 2 | 265 |1 | 266 |0 | 267 |0 | 268 |
| fit.Summary | 274 |
6 | Developers love self-referential programs! Hence, NUnit has always run all it's 7 | own tests, even those that are not really unit tests. 8 |
Now, beginning with NUnit 2.4, NUnit has top-level tests using Ward Cunningham's 9 | FIT framework. At this time, the tests are pretty rudimentary, but it's a start 10 | and it's a framework for doing more. 11 |
Open a console or shell window and navigate to the NUnit bin directory, which 13 | contains this file. To run the test under Microsoft .Net, enter the command 14 |
runFile NUnitFitTests.html TestResults.html .15 | To run it under Mono, enter 16 |
mono runFile.exe NUnitFitTests.html TestResults.html .17 | Note the space and dot at the end of each command. The results of your test 18 | will be in TestResults.html in the same directory. 19 |
| NUnit.Fixtures.PlatformInfo | 23 |
27 | Load and run the NUnit unit tests, verifying that the results are as expected. 28 | When these tests are run on different platforms, different numbers of tests may 29 | be skipped, so the values for Skipped and Run tests are informational only. 30 |
31 | The number of tests in each assembly should be constant across all platforms - 32 | any discrepancy usually means that one of the test source files was not 33 | compiled on the platform. There should be no failures and no tests ignored. 34 |
Note: 35 | At the moment, the nunit.extensions.tests assembly is failing because the 36 | fixture doesn't initialize addins in the test domain. 37 |
38 |
| NUnit.Fixtures.AssemblyRunner | 41 ||||||
| Assembly | 44 |Tests() | 45 |Run() | 46 |Skipped() | 47 |Ignored() | 48 |Failures() | 49 |
| nunit.framework.tests.dll | 52 |397 | 53 |54 | | 55 | | 0 | 56 |0 | 57 |
| nunit.core.tests.dll | 60 |355 | 61 |62 | | 63 | | 0 | 64 |0 | 65 |
| nunit.util.tests.dll | 68 |238 | 69 |70 | | 71 | | 0 | 72 |0 | 73 |
| nunit.mocks.tests.dll | 76 |43 | 77 |78 | | 79 | | 0 | 80 |0 | 81 |
| nunit.extensions.tests.dll | 84 |5 | 85 |86 | | 87 | | 0 | 88 |0 | 89 |
| nunit-console.tests.dll | 92 |40 | 93 |94 | | 95 | | 0 | 96 |0 | 97 |
| nunit.uikit.tests.dll | 100 |34 | 101 |102 | | 103 | | 0 | 104 |0 | 105 |
| nunit-gui.tests.dll | 108 |15 | 109 |110 | | 111 | | 0 | 112 |0 | 113 |
| nunit.fixtures.tests.dll | 116 |6 | 117 |118 | | 119 | | 0 | 120 |0 | 121 |
125 | These tests create a test assembly from a snippet of code and then load and run 126 | the tests that it contains, verifying that the structure of the loaded tests is 127 | as expected and that the number of tests run, skipped, ignored or failed is 128 | correct. 129 |
130 |
| NUnit.Fixtures.SnippetRunner | 133 ||||||
| Code | 136 |Tree() | 137 |Run() | 138 |Skipped() | 139 |Ignored() | 140 |Failures() | 141 |
public class TestClass
144 | {
145 | }
146 | |
147 | EMPTY | 148 |0 | 149 |0 | 150 |0 | 151 |0 | 152 |
using NUnit.Framework;
155 |
156 | [TestFixture]
157 | public class TestClass
158 | {
159 | }
160 | |
161 | TestClass | 162 |0 | 163 |0 | 164 |0 | 165 |0 | 166 |
using NUnit.Framework;
169 |
170 | [TestFixture]
171 | public class TestClass
172 | {
173 | [Test]
174 | public void T1() { }
175 | [Test]
176 | public void T2() { }
177 | [Test]
178 | public void T3() { }
179 | }
180 | |
181 | TestClass 182 | >T1 183 | >T2 184 | >T3185 | |
186 | 3 | 187 |0 | 188 |0 | 189 |0 | 190 |
using NUnit.Framework;
193 |
194 | [TestFixture]
195 | public class TestClass1
196 | {
197 | [Test]
198 | public void T1() { }
199 | }
200 |
201 | [TestFixture]
202 | public class TestClass2
203 | {
204 | [Test]
205 | public void T2() { }
206 | [Test]
207 | public void T3() { }
208 | }
209 | |
210 | TestClass1 211 | >T1 212 | TestClass2 213 | >T2 214 | >T3215 | |
216 | 3 | 217 |0 | 218 |0 | 219 |0 | 220 |
using NUnit.Framework;
223 |
224 | [TestFixture]
225 | public class TestClass
226 | {
227 | [Test]
228 | public void T1() { }
229 | [Test, Ignore]
230 | public void T2() { }
231 | [Test]
232 | public void T3() { }
233 | }
234 | |
235 | TestClass 236 | >T1 237 | >T2 238 | >T3239 | |
240 | 2 | 241 |0 | 242 |1 | 243 |0 | 244 |
using NUnit.Framework;
247 |
248 | [TestFixture]
249 | public class TestClass
250 | {
251 | [Test]
252 | public void T1() { }
253 | [Test, Explicit]
254 | public void T2() { }
255 | [Test]
256 | public void T3() { }
257 | }
258 | |
259 | TestClass 260 | >T1 261 | >T2 262 | >T3263 | |
264 | 2 | 265 |1 | 266 |0 | 267 |0 | 268 |
| fit.Summary | 274 |
6 | Developers love self-referential programs! Hence, NUnit has always run all it's 7 | own tests, even those that are not really unit tests. 8 |
Now, beginning with NUnit 2.4, NUnit has top-level tests using Ward Cunningham's 9 | FIT framework. At this time, the tests are pretty rudimentary, but it's a start 10 | and it's a framework for doing more. 11 |
Open a console or shell window and navigate to the NUnit bin directory, which 13 | contains this file. To run the test under Microsoft .Net, enter the command 14 |
runFile NUnitFitTests.html TestResults.html .15 | To run it under Mono, enter 16 |
mono runFile.exe NUnitFitTests.html TestResults.html .17 | Note the space and dot at the end of each command. The results of your test 18 | will be in TestResults.html in the same directory. 19 |
| NUnit.Fixtures.PlatformInfo | 23 |
27 | Load and run the NUnit unit tests, verifying that the results are as expected. 28 | When these tests are run on different platforms, different numbers of tests may 29 | be skipped, so the values for Skipped and Run tests are informational only. 30 |
31 | The number of tests in each assembly should be constant across all platforms - 32 | any discrepancy usually means that one of the test source files was not 33 | compiled on the platform. There should be no failures and no tests ignored. 34 |
Note: 35 | At the moment, the nunit.extensions.tests assembly is failing because the 36 | fixture doesn't initialize addins in the test domain. 37 |
38 |
| NUnit.Fixtures.AssemblyRunner | 41 ||||||
| Assembly | 44 |Tests() | 45 |Run() | 46 |Skipped() | 47 |Ignored() | 48 |Failures() | 49 |
| nunit.framework.tests.dll | 52 |397 | 53 |54 | | 55 | | 0 | 56 |0 | 57 |
| nunit.core.tests.dll | 60 |355 | 61 |62 | | 63 | | 0 | 64 |0 | 65 |
| nunit.util.tests.dll | 68 |238 | 69 |70 | | 71 | | 0 | 72 |0 | 73 |
| nunit.mocks.tests.dll | 76 |43 | 77 |78 | | 79 | | 0 | 80 |0 | 81 |
| nunit.extensions.tests.dll | 84 |5 | 85 |86 | | 87 | | 0 | 88 |0 | 89 |
| nunit-console.tests.dll | 92 |40 | 93 |94 | | 95 | | 0 | 96 |0 | 97 |
| nunit.uikit.tests.dll | 100 |34 | 101 |102 | | 103 | | 0 | 104 |0 | 105 |
| nunit-gui.tests.dll | 108 |15 | 109 |110 | | 111 | | 0 | 112 |0 | 113 |
| nunit.fixtures.tests.dll | 116 |6 | 117 |118 | | 119 | | 0 | 120 |0 | 121 |
125 | These tests create a test assembly from a snippet of code and then load and run 126 | the tests that it contains, verifying that the structure of the loaded tests is 127 | as expected and that the number of tests run, skipped, ignored or failed is 128 | correct. 129 |
130 |
| NUnit.Fixtures.SnippetRunner | 133 ||||||
| Code | 136 |Tree() | 137 |Run() | 138 |Skipped() | 139 |Ignored() | 140 |Failures() | 141 |
public class TestClass
144 | {
145 | }
146 | |
147 | EMPTY | 148 |0 | 149 |0 | 150 |0 | 151 |0 | 152 |
using NUnit.Framework;
155 |
156 | [TestFixture]
157 | public class TestClass
158 | {
159 | }
160 | |
161 | TestClass | 162 |0 | 163 |0 | 164 |0 | 165 |0 | 166 |
using NUnit.Framework;
169 |
170 | [TestFixture]
171 | public class TestClass
172 | {
173 | [Test]
174 | public void T1() { }
175 | [Test]
176 | public void T2() { }
177 | [Test]
178 | public void T3() { }
179 | }
180 | |
181 | TestClass 182 | >T1 183 | >T2 184 | >T3185 | |
186 | 3 | 187 |0 | 188 |0 | 189 |0 | 190 |
using NUnit.Framework;
193 |
194 | [TestFixture]
195 | public class TestClass1
196 | {
197 | [Test]
198 | public void T1() { }
199 | }
200 |
201 | [TestFixture]
202 | public class TestClass2
203 | {
204 | [Test]
205 | public void T2() { }
206 | [Test]
207 | public void T3() { }
208 | }
209 | |
210 | TestClass1 211 | >T1 212 | TestClass2 213 | >T2 214 | >T3215 | |
216 | 3 | 217 |0 | 218 |0 | 219 |0 | 220 |
using NUnit.Framework;
223 |
224 | [TestFixture]
225 | public class TestClass
226 | {
227 | [Test]
228 | public void T1() { }
229 | [Test, Ignore]
230 | public void T2() { }
231 | [Test]
232 | public void T3() { }
233 | }
234 | |
235 | TestClass 236 | >T1 237 | >T2 238 | >T3239 | |
240 | 2 | 241 |0 | 242 |1 | 243 |0 | 244 |
using NUnit.Framework;
247 |
248 | [TestFixture]
249 | public class TestClass
250 | {
251 | [Test]
252 | public void T1() { }
253 | [Test, Explicit]
254 | public void T2() { }
255 | [Test]
256 | public void T3() { }
257 | }
258 | |
259 | TestClass 260 | >T1 261 | >T2 262 | >T3263 | |
264 | 2 | 265 |1 | 266 |0 | 267 |0 | 268 |
| fit.Summary | 274 |
6 | Developers love self-referential programs! Hence, NUnit has always run all it's 7 | own tests, even those that are not really unit tests. 8 |
Now, beginning with NUnit 2.4, NUnit has top-level tests using Ward Cunningham's 9 | FIT framework. At this time, the tests are pretty rudimentary, but it's a start 10 | and it's a framework for doing more. 11 |
Open a console or shell window and navigate to the NUnit bin directory, which 13 | contains this file. To run the test under Microsoft .Net, enter the command 14 |
runFile NUnitFitTests.html TestResults.html .15 | To run it under Mono, enter 16 |
mono runFile.exe NUnitFitTests.html TestResults.html .17 | Note the space and dot at the end of each command. The results of your test 18 | will be in TestResults.html in the same directory. 19 |
| NUnit.Fixtures.PlatformInfo | 23 |
27 | Load and run the NUnit unit tests, verifying that the results are as expected. 28 | When these tests are run on different platforms, different numbers of tests may 29 | be skipped, so the values for Skipped and Run tests are informational only. 30 |
31 | The number of tests in each assembly should be constant across all platforms - 32 | any discrepancy usually means that one of the test source files was not 33 | compiled on the platform. There should be no failures and no tests ignored. 34 |
Note: 35 | At the moment, the nunit.extensions.tests assembly is failing because the 36 | fixture doesn't initialize addins in the test domain. 37 |
38 |
| NUnit.Fixtures.AssemblyRunner | 41 ||||||
| Assembly | 44 |Tests() | 45 |Run() | 46 |Skipped() | 47 |Ignored() | 48 |Failures() | 49 |
| nunit.framework.tests.dll | 52 |397 | 53 |54 | | 55 | | 0 | 56 |0 | 57 |
| nunit.core.tests.dll | 60 |355 | 61 |62 | | 63 | | 0 | 64 |0 | 65 |
| nunit.util.tests.dll | 68 |238 | 69 |70 | | 71 | | 0 | 72 |0 | 73 |
| nunit.mocks.tests.dll | 76 |43 | 77 |78 | | 79 | | 0 | 80 |0 | 81 |
| nunit.extensions.tests.dll | 84 |5 | 85 |86 | | 87 | | 0 | 88 |0 | 89 |
| nunit-console.tests.dll | 92 |40 | 93 |94 | | 95 | | 0 | 96 |0 | 97 |
| nunit.uikit.tests.dll | 100 |34 | 101 |102 | | 103 | | 0 | 104 |0 | 105 |
| nunit-gui.tests.dll | 108 |15 | 109 |110 | | 111 | | 0 | 112 |0 | 113 |
| nunit.fixtures.tests.dll | 116 |6 | 117 |118 | | 119 | | 0 | 120 |0 | 121 |
125 | These tests create a test assembly from a snippet of code and then load and run 126 | the tests that it contains, verifying that the structure of the loaded tests is 127 | as expected and that the number of tests run, skipped, ignored or failed is 128 | correct. 129 |
130 |
| NUnit.Fixtures.SnippetRunner | 133 ||||||
| Code | 136 |Tree() | 137 |Run() | 138 |Skipped() | 139 |Ignored() | 140 |Failures() | 141 |
public class TestClass
144 | {
145 | }
146 | |
147 | EMPTY | 148 |0 | 149 |0 | 150 |0 | 151 |0 | 152 |
using NUnit.Framework;
155 |
156 | [TestFixture]
157 | public class TestClass
158 | {
159 | }
160 | |
161 | TestClass | 162 |0 | 163 |0 | 164 |0 | 165 |0 | 166 |
using NUnit.Framework;
169 |
170 | [TestFixture]
171 | public class TestClass
172 | {
173 | [Test]
174 | public void T1() { }
175 | [Test]
176 | public void T2() { }
177 | [Test]
178 | public void T3() { }
179 | }
180 | |
181 | TestClass 182 | >T1 183 | >T2 184 | >T3185 | |
186 | 3 | 187 |0 | 188 |0 | 189 |0 | 190 |
using NUnit.Framework;
193 |
194 | [TestFixture]
195 | public class TestClass1
196 | {
197 | [Test]
198 | public void T1() { }
199 | }
200 |
201 | [TestFixture]
202 | public class TestClass2
203 | {
204 | [Test]
205 | public void T2() { }
206 | [Test]
207 | public void T3() { }
208 | }
209 | |
210 | TestClass1 211 | >T1 212 | TestClass2 213 | >T2 214 | >T3215 | |
216 | 3 | 217 |0 | 218 |0 | 219 |0 | 220 |
using NUnit.Framework;
223 |
224 | [TestFixture]
225 | public class TestClass
226 | {
227 | [Test]
228 | public void T1() { }
229 | [Test, Ignore]
230 | public void T2() { }
231 | [Test]
232 | public void T3() { }
233 | }
234 | |
235 | TestClass 236 | >T1 237 | >T2 238 | >T3239 | |
240 | 2 | 241 |0 | 242 |1 | 243 |0 | 244 |
using NUnit.Framework;
247 |
248 | [TestFixture]
249 | public class TestClass
250 | {
251 | [Test]
252 | public void T1() { }
253 | [Test, Explicit]
254 | public void T2() { }
255 | [Test]
256 | public void T3() { }
257 | }
258 | |
259 | TestClass 260 | >T1 261 | >T2 262 | >T3263 | |
264 | 2 | 265 |1 | 266 |0 | 267 |0 | 268 |
| fit.Summary | 274 |