I am happy to say that I just wrote my first dotMemory xUnit test. :) However, I wanted to see if there is an improvement I can make to this test. I am wanting to test that a certain object does NOT stay in memory. In order to do that, I have to call another method. So essentially, this creates two methods: 1 that xUnit/dotMemory calls, and then the "memory" body test.
Here is the example.
I am curious if there is a "better way" of creating this test without creating two methods. Hope this makes sense. Please let me know if you have any questions.