http://opensimulator.org/index.php?title=Talk:Automated_Testing&feed=atom&action=historyTalk:Automated Testing - Revision history2024-03-29T07:46:07ZRevision history for this page on the wikiMediaWiki 1.19.9http://opensimulator.org/index.php?title=Talk:Automated_Testing&diff=11351&oldid=prevMikem at 08:55, 12 March 20092009-03-12T08:55:16Z<p></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr valign='top'>
<td colspan='2' style="background-color: white; color:black;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 08:55, 12 March 2009</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 11:</td>
<td colspan="2" class="diff-lineno">Line 11:</td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>While my experience hasn't yet shown that test which depend on other tests are the ultimate evil, I'm confident that one should strive to avoid such a situation. The argument against chained tests stating that massive code duplication is necessary to test anything deep isn't convincing because good use of test fixture SetUp/TearDown eliminates most of the duplication.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>While my experience hasn't yet shown that test which depend on other tests are the ultimate evil, I'm confident that one should strive to avoid such a situation. The argument against chained tests stating that massive code duplication is necessary to test anything deep isn't convincing because good use of test fixture SetUp/TearDown eliminates most of the duplication.</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr>
<tr><td class='diff-marker'>−</td><td style="background: #ffa; color:black; font-size: smaller;"><div>Chained tests probably do have their place in extremely complicated systems, however I'm not convinced the components of OpenSim that are being tested have reached such a level of complexity.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>Chained tests probably do have their place in extremely complicated systems, however I'm not convinced the components of OpenSim that are being tested have <ins class="diffchange diffchange-inline">''not'' </ins>reached such a level of complexity.</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>[[User:Mikem|Mikem]] 08:54, 12 March 2009 (UTC)</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>[[User:Mikem|Mikem]] 08:54, 12 March 2009 (UTC)</div></td></tr>
</table>Mikemhttp://opensimulator.org/index.php?title=Talk:Automated_Testing&diff=11350&oldid=prevMikem: /* = */2009-03-12T08:54:31Z<p><span dir="auto"><span class="autocomment">=</span></span></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr valign='top'>
<td colspan='2' style="background-color: white; color:black;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 08:54, 12 March 2009</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 7:</td>
<td colspan="2" class="diff-lineno">Line 7:</td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>If you want to go through the unit tests and adjust them to all have Setup and Teardown methods, be my guest. :)  However it really just makes things much more difficult than they need to be, for lots of effort, and no real benefit.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>If you want to go through the unit tests and adjust them to all have Setup and Teardown methods, be my guest. :)  However it really just makes things much more difficult than they need to be, for lots of effort, and no real benefit.</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr>
<tr><td class='diff-marker'>−</td><td style="background: #ffa; color:black; font-size: smaller;"><div><del class="diffchange diffchange-inline">===</del></div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins class="diffchange diffchange-inline">---</ins></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>While my experience hasn't yet shown that test which depend on other tests are the ultimate evil, I'm confident that one should strive to avoid such a situation. The argument against chained tests stating that massive code duplication is necessary to test anything deep isn't convincing because good use of test fixture SetUp/TearDown eliminates most of the duplication.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>While my experience hasn't yet shown that test which depend on other tests are the ultimate evil, I'm confident that one should strive to avoid such a situation. The argument against chained tests stating that massive code duplication is necessary to test anything deep isn't convincing because good use of test fixture SetUp/TearDown eliminates most of the duplication.</div></td></tr>
</table>Mikemhttp://opensimulator.org/index.php?title=Talk:Automated_Testing&diff=11349&oldid=prevMikem at 08:54, 12 March 20092009-03-12T08:54:17Z<p></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr valign='top'>
<td colspan='2' style="background-color: white; color:black;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 08:54, 12 March 2009</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 7:</td>
<td colspan="2" class="diff-lineno">Line 7:</td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>If you want to go through the unit tests and adjust them to all have Setup and Teardown methods, be my guest. :)  However it really just makes things much more difficult than they need to be, for lots of effort, and no real benefit.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>If you want to go through the unit tests and adjust them to all have Setup and Teardown methods, be my guest. :)  However it really just makes things much more difficult than they need to be, for lots of effort, and no real benefit.</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr>
<tr><td class='diff-marker'>−</td><td style="background: #ffa; color:black; font-size: smaller;"><div>=<del class="diffchange diffchange-inline">= Chained tests are not necessary </del>==</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>===</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>While my experience hasn't yet shown that test which depend on other tests are the ultimate evil, I'm confident that one should strive to avoid such a situation. The argument against chained tests stating that massive code duplication is necessary to test anything deep isn't convincing because good use of test fixture SetUp/TearDown eliminates most of the duplication.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>While my experience hasn't yet shown that test which depend on other tests are the ultimate evil, I'm confident that one should strive to avoid such a situation. The argument against chained tests stating that massive code duplication is necessary to test anything deep isn't convincing because good use of test fixture SetUp/TearDown eliminates most of the duplication.</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>Chained tests probably do have their place in extremely complicated systems, however I'm not convinced the components of OpenSim that are being tested have reached such a level of complexity.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>Chained tests probably do have their place in extremely complicated systems, however I'm not convinced the components of OpenSim that are being tested have reached such a level of complexity.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">[[User:Mikem|Mikem]] 08:54, 12 March 2009 (UTC)</ins></div></td></tr>
</table>Mikemhttp://opensimulator.org/index.php?title=Talk:Automated_Testing&diff=11348&oldid=prevMikem: /* Chained tests are not necessary */ new section2009-03-12T08:53:06Z<p><span dir="auto"><span class="autocomment">Chained tests are not necessary: </span> new section</span></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr valign='top'>
<td colspan='2' style="background-color: white; color:black;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 08:53, 12 March 2009</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 6:</td>
<td colspan="2" class="diff-lineno">Line 6:</td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>If you want to go through the unit tests and adjust them to all have Setup and Teardown methods, be my guest. :)  However it really just makes things much more difficult than they need to be, for lots of effort, and no real benefit.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>If you want to go through the unit tests and adjust them to all have Setup and Teardown methods, be my guest. :)  However it really just makes things much more difficult than they need to be, for lots of effort, and no real benefit.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">== Chained tests are not necessary ==</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">While my experience hasn't yet shown that test which depend on other tests are the ultimate evil, I'm confident that one should strive to avoid such a situation. The argument against chained tests stating that massive code duplication is necessary to test anything deep isn't convincing because good use of test fixture SetUp/TearDown eliminates most of the duplication.</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">Chained tests probably do have their place in extremely complicated systems, however I'm not convinced the components of OpenSim that are being tested have reached such a level of complexity.</ins></div></td></tr>
</table>Mikemhttp://opensimulator.org/index.php?title=Talk:Automated_Testing&diff=9051&oldid=prevSeanDague at 02:49, 11 December 20082008-12-11T02:49:28Z<p></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr valign='top'>
<td colspan='2' style="background-color: white; color:black;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 02:49, 11 December 2008</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 2:</td>
<td colspan="2" class="diff-lineno">Line 2:</td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>[[User:Mikem|Mikem]] 01:01, 9 October 2008 (PDT)</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>[[User:Mikem|Mikem]] 01:01, 9 October 2008 (PDT)</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">I changed this back, because it's the way the unit tests work today.  The "theory" that no test method should depend on any other one tends to force unit tests into very shallow coverage because you would need massive code duplication to test anything deep.  My experience has shown that imposing the "no test should really on another test" generates much worse test cases.</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">If you want to go through the unit tests and adjust them to all have Setup and Teardown methods, be my guest. :)  However it really just makes things much more difficult than they need to be, for lots of effort, and no real benefit.</ins></div></td></tr>
</table>SeanDaguehttp://opensimulator.org/index.php?title=Talk:Automated_Testing&diff=7714&oldid=prevMikem at 08:01, 9 October 20082008-10-09T08:01:46Z<p></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr valign='top'>
<td colspan='2' style="background-color: white; color:black;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 08:01, 9 October 2008</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'>−</td><td style="background: #ffa; color:black; font-size: smaller;"><div>I crossed out a paragraph about naming tests a certain way in order to make sure they're run in a certain order because they depend on each other. This is bad practice. All tests should be able to run independently of one another. For any environment setup, use the SetUp and TearDown NUnit attributes. [[User:Mikem|Mikem]] 01:01, 9 October 2008 (PDT)</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>I crossed out a paragraph about naming tests a certain way in order to make sure they're run in a certain order because they depend on each other. This is bad practice. All tests should be able to run independently of one another. For any environment setup, use the SetUp and TearDown NUnit attributes.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>[[User:Mikem|Mikem]] 01:01, 9 October 2008 (PDT)</div></td></tr>
</table>Mikemhttp://opensimulator.org/index.php?title=Talk:Automated_Testing&diff=7713&oldid=prevMikem at 08:01, 9 October 20082008-10-09T08:01:33Z<p></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr valign='top'>
<td colspan='2' style="background-color: white; color:black;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 08:01, 9 October 2008</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'>−</td><td style="background: #ffa; color:black; font-size: smaller;"><div>I crossed out a paragraph about naming tests a certain way in order to make sure they're run in a certain order because they depend on each other. This is bad practice. All tests should be able to run independently of one another. For any environment setup, use the SetUp and TearDown NUnit attributes.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>I crossed out a paragraph about naming tests a certain way in order to make sure they're run in a certain order because they depend on each other. This is bad practice. All tests should be able to run independently of one another. For any environment setup, use the SetUp and TearDown NUnit attributes. <ins class="diffchange diffchange-inline">[[User:Mikem|Mikem]] 01:01, 9 October 2008 (PDT)</ins></div></td></tr>
</table>Mikemhttp://opensimulator.org/index.php?title=Talk:Automated_Testing&diff=7712&oldid=prevMikem: New page: I crossed out a paragraph about naming tests a certain way in order to make sure they're run in a certain order because they depend on each other. This is bad practice. All tests should be...2008-10-09T07:58:36Z<p>New page: I crossed out a paragraph about naming tests a certain way in order to make sure they're run in a certain order because they depend on each other. This is bad practice. All tests should be...</p>
<p><b>New page</b></p><div>I crossed out a paragraph about naming tests a certain way in order to make sure they're run in a certain order because they depend on each other. This is bad practice. All tests should be able to run independently of one another. For any environment setup, use the SetUp and TearDown NUnit attributes.</div>Mikem