Hi Sven,
To help repro the issue I will need a simple test that does as your describe at your end.
Can you for testing purposes reduce your tests to a small subset (say 10) that have no database access. Run these through and see if they run ok with reports etc. If these run ok then add in 10 more tests with database access and so on. I need to check that it's not a load issue nor a threading issue with COM. If you get the issue in the first 10 then reduce to 5 and if you still get the issue then can simplify the test's for repro here.
Thanks
Andy
On 9/12/06, Sven <[EMAIL PROTECTED]> wrote:
Hello Ben,
In most cases it stop after all tests have finished before creating the
report.
The test don't involve HTTP requests but database connections using
oledb and sqlserver access. I'm also using Enterprise Services for some
transactions but I have had the problem before using Enterprise
Services, too. Yes I'm using an older version of TD.net addin.
I would be happy if we could eliminate this problem because the nigthly
builds often hangs, so if you have further questions about it I will
try to answer them as detailed as possible.
Thanks,
Sven
Ben Hall wrote:
> Hello Sven,
>
> Thanks for your email.
>
> I haven't looked at MB-39, so flying blind with the questions at the
> moment. The number of tests shouldn't be a problem as I have used a
> test suite with MbUnit with around 500 tests without any problems at
> all.
>
> If you don't mind answering some initial questions, it will help me
> when looking into the problem (hopefully sometime this week, but I
> can't promise).
>
> Does it stop at any particular point/test? What kind of tests are you
> using, do they involve HTTP requests, database connections, any
> external services?
>
> When you mention running it within Team Edition, are you using the TD.net addin?
>
> Thanks
>
> Ben
>
>
> On 11/09/06, Sven <[EMAIL PROTECTED] > wrote:
> >
> > Hi,
> > I have some issues when running tests.
> >
> > 1. When running tests using the msbuild tasg of mbunit the test
> > execution often hangs. I can't say exactly when it happens. Very often
> > all tests were executed the last message was the summary and no report
> > was be created. In some cases when deleting the output directory the
> > task ends successfully. But in some cases the task hangs after a view
> > tests were executed and some remain to be executed.
> > Before using the mbunit msbuild task, I used the mbunit console
> > application with an separate file containing a list of all assemblies
> > to be tested and I have had the same behaviour. Sometimes the tests
> > hangs when running from within VS 2005 Developer Team Edtion.
> > Any idea?
> >
> > 2. When the tests have finished and the html report was generated
> > successfully the report doesn't looks as expected. The Html report
> > repeats information. The result is the same as described in MBUNIT-39
> > (Core, NAnt-Task). Seems to be a general issue - not just limited to
> > NAnt-Task.
> >
> > Maybe some facts will help:
> > Used MbUnit Version 2.3.71
> > No of tests: about 200
> >
> > Thanks for your help.
> > Sven
> >
> >
> > >
> >
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
