Hi Kevin,
Your code works fine, I think its just the way the UI displays the tests.
When I run it, I get a single test but with the name:
GetConfigurationsTest.LogonFailTest.LogonPassTest
When one of the test fails, they all fail. So it looks to work, just
an odd way of showing it on the UI.
The same with TestDriven
MbUnit 1.0.2574.17177 Addin
Found 1 tests
[success] TestWebService.GetConfigurationsTest.LogonFailTest.LogonPassTest
[reports] generating HTML report
Maybe the way we should a TestSequence could be a lot better....
Hope this helps.
Ben
On 10/04/07, Kevin <[EMAIL PROTECTED]> wrote:
>
> [ProcessTestFixture]
> public class TestWebService
> {
>
> [TestSequence(3)]
> public void LogonPassTest()
> {
> //blah
> }
>
> [Test]
> [TestSequence(2)]
> [ExpectedException(typeof(SoapException))]
> public void LogonFailTest()
> {
> //blah }
>
> [Test]
> [TestSequence(1)]
> public void GetConfigurationsTest()
> {
> //blah
> }
> }
>
> In the above code only LogonPassTest shows up in the GUITestRunner.
> Disassembly of the compiled code shows that the attributes are tagged
> properly on the methods.
> Is this a known bug?
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"MbUnit.User" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/MbUnitUser?hl=en
-~----------~----~----~----~------~----~------~--~---
