sut | Simple universal time - Have a look

The definition of CreateLockAsync

Replace = with : in setUp() while creating sut object.

The delegate is not being declared correctly

In general, the approach to testing with fakes is

1. create a fake object to abstract away your system under test's collaborator
2. optionally configure the fake's behaviour
3. create the system under test and provide the fake
4. exercise the system under test
5. optionally interrogate the fake

You're missing part 1, part of 3 (the "providing" part), and part 5 is slightly off. I don't know what x represents in your code, but you'd need to fake whatever type it is, and ensure that the fake is provided to the foo instance. Then you'd have something like

First of all, since your unit under test is the Contacts class there is no need to spy on it and mock its behavior as this is the class you need to test. So, I would go ahead and remove that.

Now regarding your question, what you need to test is the actual outcome of the getUser, so the simplest of all tests would be to invoke the method on an instance of Contacts and assert that the returned result is a non-null instance of a User object.

If you really want to test that the constructor of the User class gets called, you will need to actually mock that call using either PowerMock (which is advise against and most likely does not even work with JUnit5) or use mockito-inline.

Once this is done you would be able to return a mocked User instance from the constructor call which you can then run assertions on.

The scenario you describe sounds like a good use case for the MemberAutoDataAttribute. This attribute is similar to the MemberDataAttribute from xUnit, and it should allow you to provide parameters to a test method from a static member (field/property/method).

There is currently a bug in the MemberAutoDataAttribute where it provides only the first set of parameters from the member. There is a workaround published by a community member here.

I will try to get a fix out for the attribute soon.

When I face challenges like this, I reach for two tools:

1. Executing the run loop
2. Putting the view controller's view into a real window

I wrote a unit test that didn't work, then tried these tricks. The window trick worked.

Alternative approach tp introduce a class to represent section of the configuration, then use IOptions interface to inject it to the constructor.

Your tests then become simple to configure without mocking, just create an instance and pass it to the constructor.

Something like below:

There are several issues here.  The main one is:

Because you've redirected System.out, the print() in your test method goes to outContent, along with the output from FirstClass.main() that you want to test, instead of to the screen or wherever you want it.

I can see two fixes for this.

The quick one is for your test method to output to originalOut: