Hello, I am experiencing a bizarre issue when running unit tests via the GUI. When I navigate to the DLL and run tests this works fine however when I generate an nunit project and run it, I get failing tests. See below for replication steps.

1. Downloaded version 2.6.4 of the nUnit.
2. Opened a Unit Test DLL and run the tests via the GUI.
3. All these tests pass.
4. File > Save as a "nunit package".
5. Open the project and run.

I get a different output as in tests start failing. Seems as though it's referring to a config section which its trying to get a hold of but hasn't packaged this correctly? I am speculating but would appreciate some assistance as to why this is happening and what the difference is between the two.

Since NUnit and the adapter have different release cycles, it will be more convenient for the adapter to be in a different directory structure.

This duplicates what we maintain on the wiki.

When fixing #28 - found that there were two copies of the file under v2.6 and v3.0.

I only fixed the v2.6 copy, are the 3.0 docs in this repo now redundant, and can we remove them?

Directory Assert will have to be re-added, since it was removed. You can copy from 2.6.3.
You might combine file and directory assert in one page, but we could also leave that for the beta docs, which will likely be in a new form.

@raad9 commented on Wed Nov 18 2015

i am able to inject any html code with this vulnerability on this page : http://nunit.org/?p=

the variable "p" is vulnerable .

So what i can do with this ? it's easy to help me steal users cookies , by injecting an "img" tag with attribute "src" that reffer to some page i made it to steal cookies .

Example :
http://nunit.org/?p=

@CharliePoole commented on Wed Nov 18 2015

Thanks for pointing that out. I'll run some tests.

@raad9 commented on Wed Nov 18 2015

you are welcome :)

@rprouse commented on Sat Dec 05 2015

While it is vulnerable to that attack, AFAIK, there are no cookies that are of any value on the NUnit website. I think the only cookies that get stored are your preferred programming language for the code examples.

Also, there is no way for users to post comments on the site, so I believe that the only way to exercise this vulnerability is through cross-site links as above.

Am I missing a way of exploiting this that exposes more sensitive information? I guess they could possibly inject javascript to rewrite some of the dom to inject links or text that looks like it came from us.

We should fix this, but I would rather see it fixed by finally getting the new website out 😄

@CharliePoole commented on Sat Dec 05 2015

I figured I'd step through and see what we do with the two or three variables we pull from the URL.

This relates to transfering responsibility for the website from me personally to the core team or webmaster. It does not relate to any design or technical issues beyond separating out stuff that is mine from stuff that is nunit's and figuring out who gets what content.

It will also relate to dealing with my own copyright on some of the material so that the nunit organization is able to use it.

From the mailing list,

The following block of code should be changed from

private void WriteToConsole(string eventMessage, TestDetails details)
    {
        Console.WriteLine("{0} {1}: {2}, from {3}.{4}.",
            eventMessage,
            details.IsSuite ? "Suite" : "Case",
            _Message,
            fixture != null ? fixture.GetType().Name : "{no fixture}",
            method != null ? method.Name : "{no method}");
    }

to

private void WriteToConsole(string eventMessage, TestDetails details)
    {
        Console.WriteLine("{0} {1}: {2}, from {3}.{4}.",
            eventMessage,
            details.IsSuite ? "Suite" : "Case",
            _Message,
            details.Fixture != null ? details.Fixture.GetType().Name : "{no fixture}",
            details.Method != null ? details.Method.Name : "{no method}");
    }

See nunit/nunit#1854

Remove references to gui and pnunit

The project organization on GitHub has changed

We have discussed this several times in the mailing list, but haven't made any progress, so I wanted to capture the discussion here. We can change the title of the issue once we make a final decision on how we want to proceed.

The options we have talked about are;

• Move our documentation and possibly the entire NUnit site to use GitHub pages
• Host the documentation in one of the GitHub repository wikis
• Others?

I read a blog post this morning about how GitHub uses GitHub pages to provide all the documentation for GitHub. Their documents are also versioned which would be useful for us. The blog post might give us some direction, https://github.com/blog/1939-how-github-uses-github-to-document-github

I'm not sure if this issue belongs here or in the main repository where we can track it with the release milestones.

Should reflect what you do with 32/64 bit selection

I propose an update and upgrading the site to new web standards and design

License says it's for NUnitLite and the copyright line has the wrong dates

The NuGet packages point to the license in the nuget folder of the site. We should either add the MIT license for v3 or replace the existing license. If the license is added, the nuspec files in the framework project will need to be updated accordingly.

Remove all references to the Gui. Describe various ways to install NUnit 3.0.

Combined notes should list everything that is new from 2.6.3 in one place.
Allow switching between combined and detailed as in earlier releases

The site was started when NUnit was just NUnit. When we added the VS adapter, we had two products and that didn't seem like enough to add a Products menu. Now (suddenly?) we have a bunch of things so it's past due.

My general idea is that there will be a top-level product menu with all the info (docs, downloads, etc.) for a single product on a page.

I view this as content reorganization. Any changes to the appearance can come separately, later.

Need to add recent donations.

Document custom attributes, including action attributes and those that replace addins.
Explain how addins have gone away and how to convert from old to new model.
Update custom constraints page

Noticed doing #53 that the adapter links on the http://nunit.org/index.php?p=download are a few versions behind.

I haven't 'just fixed them' - as I wasn't sure if people would prefer them to be removed instead, if keeping them up-to-date is becoming an extra cost. @OsirisTerje @CharliePoole?

The other alternative of course, is we take the version numbers/release dates off this page, and just have it point to the latest version.