Question on the Reqnroll Sample ReqOverflow

[andre2test]

I am using as a template the Reqnroll sample project ReqOverflow. I am having difficulties getting the ActionAttemptFactory to setup a container with the ErrorMessageProvider and TestLogger instances registered. I slightly changed the TestLogger class to write to a log rather than to console. Where/how does the Sample Reqnroll register the ErrorMessageProvider and TestLogger instances to the IObjectContainer? How does the ActionAttemptFactory get called. Just having a rough time wrapping my mind around how this works.

[clrudolphi]

I'm not entirely familiar with that sample, but in looking over the source, I see in the ActionAttempt.cs file that it explicitly implements the IContainerDependentObject interface operation called SetObjectContainer. The code within ActionAttempt looks like this:

        // SpecFlow calls this method when the object is created, so you can get
        // additional dependencies without passing them through the derived ctor
        void IContainerDependentObject.SetObjectContainer(IObjectContainer container)
        {
            _errorMessageProvider = container.Resolve<ErrorMessageProvider>();
            _testLogger = container.Resolve<TestLogger>();
        }

This method is invoked by the ActionAttemptFactory in this line of the Create function:

        public ActionAttempt<TInput, TResult> Create<TInput, TResult>(string name, Func<TInput, TResult> action)
        {
            if (name == null) throw new ArgumentNullException(nameof(name));
            if (action == null) throw new ArgumentNullException(nameof(action));

            var result = new ActionAttempt<TInput, TResult>(action, name);
            ((IContainerDependentObject)result).SetObjectContainer(_container);
            return result;

It seems that the ActionAttemptFactory is then a base class for each of the three sample test suites. For example, in the ReqOverflow.Specs.API project, there is an UserAPIDriver.cs that calls the CreateWithStatusCheck method of the ApiActionAttemptFactory, which in turn calls the Create method of the ActionAttemptFactory as shown above.

The UserAPIDriver class is a class constructor argument to the [Binding] class RegistrationStepDefinitions. So when Reqnroll starts the execution of ReqOverflow.Specs.API, it will create an instance of RegistrationStepDefinitions and in turn that will create an instance of UserAPIDriver.

Also, from a quick search of the code base, I can find no specific spot where an instance of the TestLogger is registered with the IObjectContainer. So it is creating one when needed. If you've modified the TestLogger, it should be created automatically. But you'll need to repeat the implementation in all three testing projects (API, Controller, and Web), as they're basically copies of each other.

HTH

[andre2test]

Thanks you for reviewing my question. What I am doing is following the pattern of the sample as it represents a cool and modern way to set up POM files where different interactive flow sequences can be made into events and coordinated by a corresponding context class. I got a functional workaround where I check in ActionAttempt if the TestLogger is null; if it is, then I instantiate it. It works well now, so I am happy. Like yourself, I did not find how the TestLogger is registered with the Ioc Container.

[clrudolphi]

Because the code is asking the container to resolve a Type and not an interface, it doesn't have to be registered. The container will instantiate an instance of the type when needed.