Recent changes to feature-requests

Download reflector through proxy

2003-07-18T14:16:44Z

After the installation of the last package
(ManagedAddIns-1.0.33.msi) I filled in the download form
for reflector but failed because I have to pass a firewall
with authentication.

I've changed the files
RegisterForm.cs and
ReflectorInstaller.cs
and attached them to work around the problem.

It would be nice, if you could integrate the changes.

Markus

Re-Run last test

2003-04-11T11:35:35Z

It would be nice to have a command to re-run the last test.
Not necessarily a button or a context menu item, just a
command that could be bound to a keyboard shortcut
(that's where it would end up anyway).

Show the Red/Yellow/Green Status

2003-03-18T21:12:28Z

I would like to see the colors. While it is *very* helpful
for the test information to appear in the build window, I
think it would also be helpful if an optional GUI
component (throught a checkbox on a property page,
perhaps) could be shown with the Red, Yellow, or Green
test status bars.

Debug Tests in Popup menu

2003-03-09T04:41:55Z

Small feature request. I'd like to see the Debug Tests
verb in the right-click popup menu instead of just under
tools.

Build with NUnit Addin does not save files

2003-02-10T15:03:45Z

There is an option in the VS .NET settings to save
source files when doing a build. The NUnit Addin should
use those settings and save source files when it does a
build as well.

Register test assembly for non-test projects

2002-12-31T19:30:38Z

I would like to register a test assembly (either a project
in the solution or an external DLL) for projects that aren't
themselves test assemblies.

The ideal use case is where I'm working on my code,
then with a single keystroke build my code and run the
unit tests for it. To do this, if the NUnitAddin already
knows the correct test assembly to run (because I've
registered it), I could replace the key binding for build
project with the addin's build & test command.

Alternatively, the addin could be set up to catch build
events and run the test after every successful project
build.

output results to file

2002-12-09T22:06:17Z

It would be nice to have an option to output the
results to a file which visual studio would
immediately open, rather than a standard output
window.

(I am thinking of something along the lines of the
way the tools->build comment web pages works)

With an approriate stylesheet, it would be possible
to have much nicer-looking and easier to read test
results, particularly when we are talking about large
numbers of tests.

A good example is the tests results generated for
the eclipse project. Here is one such page:

http://download.eclipse.org/downloads/drops/N-
N20021209-
200212090010/testresults/org.eclipse.jdt.ui.tests.r
efactoring_linux-motif.html

(also attached)

Execute code snippit

2002-11-27T20:24:49Z

I want to highlight a piece of code and choose to
execute the snippit in the test window.

Use the code compile model. See....

Building a .NET Shell-Level Infrastructure for C# Scripts
slides - 737 kb
code - 5 kb
http://www.sigs.de/download/dotnet_02/di09_esposito_sl
ides.zip
http://www.sigs.de/download/dotnet_02/di09_esposito_s
ource.zip
http://www.sigs.de/download/dotnet_02/index.htm

Build before running/debugging tests

2002-11-21T13:38:54Z

Is it possible to do a "Build Solution" automatically
before tests are run?

I can understand that this would be anoying overhead if
you run a number of individual tests, but I also find it
anoying to have to build manually in my code/test cycle.

I feel a program is verified for correctness in a number of
steps.
1. build it, this catches compiler errors
2. unit test it, this catches errors in the implementation
of the spec
3. user test it, this catches errors in the specification of
the requirements

I feel that any level has to be preceded by lower levels.
Don't user test unless you unit tested. Don't unit test
unless you compiled.

Note that I ask for a "Build", not a "Rebuild".
Theoretically, a build of only those assemblies that
contain tests is sufficient. Maybe this can be detected
easily when a reference to ununit.framework is found in
the project.

Comments?