johannesegger / extracttypetofilediagnostic Goto Github PK

Assert that executing both fixes should extract the types into TypeA.cs

If a fix extracts a type into an existing file, the type should be integrated in a clean way.
If the namespace exists, put it in it.
Otherwise create the namespace declaration and put the type in it.
Also handle nested namespaces.
Non-existing using directives should be added.

Due to the fact, that we remove and add a document when we want to rename it, Visual Studio closes the document. I couldn't find a way to cleanly rename a file. I tried to add a document with the same id, but VS doesn't seem to like that because it crashed. I also tried to use solution.Workspace.OpenDocument(documentId) as a work-around, but nothing happened.

There are a lot of repeating code segments which decrease maintainability.

• Use NUnit's parameterized tests to create test data or
• Extract common code segments into helper methods and use them from within the tests.

The first option is currently preferred as the basic structure is always the same:

• Setup solution
• Get diagnostics and compare with expected
• Apply fixes and compare resulting solution with expected solution
• Get diagnostics and assert there are none.

When there's only a single non-nested type within a file, the result should be a simple rename of the file.