Closed GoogleCodeExporter closed 9 years ago
Original comment by grahamr...@gmail.com
on 11 Mar 2010 at 7:59
Make sure that you have instructed Icarus to use the AutoCAD test runner
factory or
it won't create an AutoCAD process to run the tests in.
In the build I'm running (v3.2 b283) this is under Icarus/Runner/Test Runner
Factory
in the control panel.
I think it might be under "Test Explorer Options" or something similar in v3.1.
Original comment by mikesand...@gmail.com
on 11 Mar 2010 at 8:10
Another one for the wiki :)
Original comment by grahamr...@gmail.com
on 11 Mar 2010 at 8:26
I should figure out a way for Gallio to recognize that the test assembly will
need
AutoCAD and automatically use the AutoCAD runner. This has tripped up more than
a few
people.
Could look for an assembly reference to one of the AutoCAD assemblies perhaps.
It'd
also have to run at some stage before exploration since that needs to run inside
acad.exe...
Original comment by mikesand...@gmail.com
on 11 Mar 2010 at 8:34
Sounds like a good idea!
Original comment by grahamr...@gmail.com
on 11 Mar 2010 at 9:17
Here's the conversation...
You could try reflection. Kean and I thought about this for installation
purposes
and he posted a solution here:
http://through-the-interface.typepad.com/through_the_interface/2010/02/creating-
demand-loading-entries-for-net-modules-outside-of-autocad.html
A module will have a CommandMethodAttribute if they are trying to create a
command
usable in AutoCAD.
-----Original Message-----
From: mb-unit@googlecode.com [mailto:mb-unit@googlecode.com]
Sent: Thursday, March 11, 2010 3:36 PM
To: dave.wolfe.ecad@gmail.com
Subject: Re: Issue 635 in mb-unit: AutoCAD not testing a dll
Comment #4 on issue 635 by mikesand...@gmail.com: AutoCAD not testing a dll
http://code.google.com/p/mb-unit/issues/detail?id=635
I should figure out a way for Gallio to recognize that the test assembly
will need
AutoCAD and automatically use the AutoCAD runner. This has tripped up more
than a few
people.
Could look for an assembly reference to one of the AutoCAD assemblies
perhaps. It'd
also have to run at some stage before exploration since that needs to run
inside
acad.exe...
Original comment by dave.wo...@outlook.com
on 11 Mar 2010 at 9:20
Something else that would be really cool for AutoCAD testing would be to allow
targeting multiple versions of AutoCAD. For example, often developers end up
supporting AutoCAD 2008, AutoCAD 2009, AutoCAD 2010, etc. It's really annoying
setting
up the same tests to run in 3 different versions, or to have to switch the
environment
to run the tests. May if we could specify in our test fixture a list of exe's
to
launch, and then be able to click run and have the test run on Acad 08, then
Acad 09,
etc. Also, it'd be nice to have an attribute to let us exclude from a certain
exe, as
sometime the AutoCAD api breaks between versions. Is this too much rambling?
Original comment by dave.wo...@outlook.com
on 15 Mar 2010 at 6:03
Original comment by mikesand...@gmail.com
on 21 Mar 2010 at 8:26
Original issue reported on code.google.com by
dave.wo...@outlook.com
on 11 Mar 2010 at 7:11Attachments: