How to implement customize output for pact?

Hi Brother,

How to implement customize output for PactVerifierConfig , currently i use NUnit test framework in out project , and i want to output the pact test result in unit test window, but it didn’t work , can you give some demo code to handle it , thanks .

currently code as bellow:

`

        const string serviceUri = "http://localhost:51502";

        var config = new PactVerifierConfig
        {
            Outputters = new List<IOutput>
                              {
                                  new ConsoleOutput()
                              }
        };

        IPactVerifier pactVerifier = new PactVerifier(config);
        pactVerifier
            .ServiceProvider("Event API", serviceUri)
            .HonoursPactWith("Event API Consumer")
            .PactUri("userclient-userservice.json")
            .Verify();
    }`

ConsoleOutput implementation

public class ConsoleOutput: IOutput { public void WriteLine(string line) { Console.WriteLine(line); } }

when i run the test , it will throw the exception : PactNet.PactFailureException : Pact verification failed. See output for details. If the output is empty please provide a custom config.Outputters (IOutput) for your test framework, as we couldn't write to the console.

[neilcampbell]

Thanks for the detailed reply.

The ConsoleOutput is registered by default, and works for most test frameworks. xUnit however redirects the stdout and therefore the default handling does not work. See https://stackoverflow.com/questions/7138935/xunit-net-does-not-capture-console-output. When using xunit you need to provide a custom outputter, not the included ConsoleOutput. If you search the readme or samples for “XUnitOutput”, you can see an example of how this is done. That should hopefully get you the details about why the exception was actually thrown.

[neilcampbell]

@andreimcristof A PactFailure exception is thrown when something fails to be performed correctly, in Ken’s case the “Pact verification failed”. The “Note” part of that message is just saying that if you see no details about why the failure occurred, you may need to register a custom outputter. Not registering a custom outputter will never be the cause of an exception. The “Note” part is always written, regardless of test framework and if you have registered one or not, as we don’t know the runtime config at the time the exception is thrown. Does that make sense? Any suggestions to make this clearer?