The absense of a TestFixture attribute is not going to crash NUnit. Charlie
On Wed, Oct 10, 2012 at 7:52 PM, Jv <jv.ravichand...@gmail.com> wrote: > It may be related to the AppDomain (s) that are being used. > > Are you sure the attribute on your class is [TestFixture] when you run the > test in NUnit? > > Jv > > On Thu, Oct 11, 2012 at 7:06 AM, Mun Wai Chan > <mun...@globesoftware.com.au>wrote: > >> Hi Jv, >> >> >>1. When working in the unmanaged context, it is worth trying the >> STAThread >> attribute on the method. >> >> Tried adding this and it still crashes. >> >> >>2. Try adding a role for the user with ax32.exe (if it already exists, >> please post the role). Plus test permission sets and any admin tasks that >> was done during installation of Ax. >> >> I am a domain and Ax admin. >> >> >>3. It looks like with messages on "marshalling" and Domain usage: Single, >> it could well be related to the CLR, the GAC and the Dll context. These are >> vague references that can be clarified if you walk us through your >> installation type of AX, the CLR version, the roles and permission sets. >> >> The thing is why does it work for MSTest but not NUnit? Which makes me >> think that it is not related to permissions. >> >> Thanks, >> >> Mun Wai >> >> -- >> You received this bug notification because you are a member of NUnit >> Developers, which is subscribed to NUnit V2. >> https://bugs.launchpad.net/bugs/1064804 >> >> Title: >> Test throws an exception in NUnit but works when running in MSTest or >> as a Console application >> >> Status in NUnit V2 Test Framework: >> New >> >> Bug description: >> Hi, >> >> I have a simple test which throws an error when I run it using NUnit >> (fails on both NUnit GUI/console and Resharper in VS). However, if ran >> using Visual Studio's Test -> Debug option or as a Console >> application, it runs fine. The code is exactly the same for the 3 >> different projects types (NUnit, Console and MSTest). >> >> Source code for NUnit test: >> >> using System.Net; >> using Microsoft.Dynamics.BusinessConnectorNet; >> using Microsoft.VisualStudio.TestTools.UnitTesting; >> >> namespace TestProject1 >> { >> [TestClass] >> public class UnitTest1 >> { >> [TestMethod] >> public void TestMethod1() >> { >> Axapta ax = new Axapta(); >> ax.LogonAs("User1", "Globe", new NetworkCredential("User1", >> "pwd", "Globe"), default(string), default(string), >> "A6BuildTestAos:6004", default(string)); >> ax.Logoff(); >> } >> } >> } >> >> Error: >> >> FatalExecutionEngineError was detected. >> The runtime has encountered a fatal error. The address of the error was >> at 0x5785ca87, on thread 0x792c. The error code is 0xc0000005. This error >> may be a bug in the CLR or in the unsafe or non-verifiable portions of user >> code. Common sources of this bug include user marshaling errors for >> COM-interop or PInvoke, which may corrupt the stack. >> >> Thanks in advance. >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/nunitv2/+bug/1064804/+subscriptions >> > > > -- > Regards, > > Ravichandran Jv > http://ravichandranjv.blogspot.com > > -- > You received this bug notification because you are subscribed to NUnit > Extended Testing Platform. > https://bugs.launchpad.net/bugs/1064804 > > Title: > Test throws an exception in NUnit but works when running in MSTest or > as a Console application > > To manage notifications about this bug go to: > https://bugs.launchpad.net/nunitv2/+bug/1064804/+subscriptions -- You received this bug notification because you are a member of NUnit Developers, which is subscribed to NUnit V2. https://bugs.launchpad.net/bugs/1064804 Title: Test throws an exception in NUnit but works when running in MSTest or as a Console application Status in NUnit V2 Test Framework: New Bug description: Hi, I have a simple test which throws an error when I run it using NUnit (fails on both NUnit GUI/console and Resharper in VS). However, if ran using Visual Studio's Test -> Debug option or as a Console application, it runs fine. The code is exactly the same for the 3 different projects types (NUnit, Console and MSTest). Source code for NUnit test: using System.Net; using Microsoft.Dynamics.BusinessConnectorNet; using Microsoft.VisualStudio.TestTools.UnitTesting; namespace TestProject1 { [TestClass] public class UnitTest1 { [TestMethod] public void TestMethod1() { Axapta ax = new Axapta(); ax.LogonAs("User1", "Globe", new NetworkCredential("User1", "pwd", "Globe"), default(string), default(string), "A6BuildTestAos:6004", default(string)); ax.Logoff(); } } } Error: FatalExecutionEngineError was detected. The runtime has encountered a fatal error. The address of the error was at 0x5785ca87, on thread 0x792c. The error code is 0xc0000005. This error may be a bug in the CLR or in the unsafe or non-verifiable portions of user code. Common sources of this bug include user marshaling errors for COM-interop or PInvoke, which may corrupt the stack. Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/nunitv2/+bug/1064804/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~nunit-core Post to : nunit-core@lists.launchpad.net Unsubscribe : https://launchpad.net/~nunit-core More help : https://help.launchpad.net/ListHelp