konrad-kruczynski/covrin

Universal code coverage tool for .NET

covrin's Issues

Add BlockEntry.LastInstruction to point to the beginning of the last instruction

and move Length to be dynamically calculated

Add build directory

With all decorated binaries, default config and required references

Write analysed data to a file

Decide what to do with jumps to next instruction

Should we leave it as one block?

I believe it's not that important at the moment. After all, it's only one additional block.

Mark and verify modified binary

Such a binary should not be analyzable anymore

Support switch in Analyzer

It's Operand is actually an array of Instructions.

Verify if added references have to be in the same directory

Let's imagine that we run:

Runner.exe some.dll dir/other.dll

As a result we'll have:

build
-> some.dll
-> dir/other.dll
-> Migrant.dll
-> Writer.dll
-> other stuff

Will it work for other.dll?

What if we add only dir/other.dll? Currently we recreate the directory structure (not perfectly tough).

Analyze the following case

I have found it interesting to test, but I have too slow an ssh connection to test it properly. Leaving sources here:

public static void Main (string[] args)
{
    var output = 0;
    var input = Int32.Parse(Console.ReadLine ());
    switch (input) {
    case 1:
        output += 5;
        break;
    case 23:
        output += 191;
        break;
    case 5:
        output += 91;
        break;
    case 2:
        output += 9;
        break;
    case 3:
        output += 10;
        break;
    }
    Console.WriteLine (input);
}

Secure Writer multithread access

Support nested types in Decorator

Employ FluentIL or find alternative for tests

Rework BlockEntry to contain namespace elements

Create test project and add tests for IntervalCollection

Writer stub

• should use PrimitiveWriter from Migrant
• should write visited block id's
• should have static class for writing (possibly delegating to another dll)

Add option to Runner to analyze different stuff

• one assembly
• a directory (recursively)
• many assemblies

IntervalCollection::Insert: prevent overlapping

Just throw an internal error (e.g. IOE exception) in such case.

Create Viewer stub in XWT

Should contain:

• open button
• progress bar
• type browser tree on the left
• every namespace element as a node with (+)
• list down to every method
• percentage for each node
• sources in IL with some stats

Write tests for Decorator

Possibly without any tmp files.

What is the -s option for?

You can change the settings file name, true. But what then? Writer would still try to access the old one. Was your idea to alter Writer as well?

Decorate binaries with log points

Create tests for block creation

Check if splitting works correctly etc

IntervalCollection::Insert put the new interval in the correct position instead of sorting

Decide what to do with AssemblyInfos

Expand writer stub with options

• flush after each write (default: disabled)
• append/overwrite results (default: append)
• file log localisation and name (with some default)

With our own parsing, as simple as possible