42 lines
1.8 KiB
Gherkin
42 lines
1.8 KiB
Gherkin
Feature: Application Container Dependency Injection Coverage
|
|
As a developer
|
|
I want to ensure the application container properly manages service dependencies
|
|
So that all container methods and singleton patterns are thoroughly tested
|
|
|
|
@phase1
|
|
Scenario: Container settings method returns valid application settings
|
|
Given I have initialized an application container
|
|
When I request the application settings from the container
|
|
Then the container should return valid settings object
|
|
|
|
@phase1
|
|
Scenario: Container project service method creates and returns service instance
|
|
Given I have initialized an application container
|
|
When I request a project service from the container
|
|
Then the container should return a valid project service instance
|
|
|
|
@phase1
|
|
Scenario: Container context service method creates and returns service instance
|
|
Given I have initialized an application container
|
|
When I request a context service from the container
|
|
Then the container should return a valid context service instance
|
|
|
|
@phase1
|
|
Scenario: Container plan service method creates and returns service instance
|
|
Given I have initialized an application container
|
|
When I request a plan service from the container
|
|
Then the container should return a valid plan service instance
|
|
|
|
@phase1
|
|
Scenario: Get container function creates singleton on first call
|
|
Given no global container exists
|
|
When I access the global container for the first time
|
|
Then a new container instance should be created and cached
|
|
And subsequent accesses should return the same instance
|
|
|
|
@phase1
|
|
Scenario: Reset container function clears singleton for testing
|
|
Given a global container exists
|
|
When I reset the global container
|
|
Then the global container should be cleared
|
|
And the next access should create a new instance |