Goal
Expand the smoke-test suite created by #49 with additional scenarios for essential integrations of the current Nextcloud stack.
#49 creates the test foundation and verifies the minimum case: the stack starts and Nextcloud reaches an installed state.
This issue adds coverage for Redis and the web layer using the same test suite.
Scope
Reuse the test framework, setup, isolation, cleanup, and local test command introduced by #49 .
Add two focused scenarios:
Nextcloud can reach the configured Redis service;
the web layer can reach and serve the running Nextcloud instance.
Do not create another test runner or a separate test environment.
Scenario: Redis integration
Verify that the Redis service used by the current stack is reachable from the running Nextcloud environment.
The test must validate the connection expected by the stack, not only that the Redis container itself is running.
Keep the scenario limited to basic connectivity. Do not test Redis features, performance, or failure recovery.
Scenario: web integration
Access Nextcloud through the web service defined by the current Compose stack.
Verify that the web layer can reach the application and return a valid HTTP response from the running Nextcloud instance.
Keep the scenario at the HTTP/runtime level. Browser automation and application workflows are outside this smoke-test suite.
Test suite reuse
The new scenarios must be part of the same smoke-test suite created by #49 .
The same documented local command must run the complete suite.
Reuse shared setup, teardown, readiness, and diagnostic helpers where appropriate.
GitHub Actions is not part of this issue. CI integration will later execute the same test suite.
Isolation and cleanup
Keep the isolation guarantees established by #49 .
The tests must not depend on an existing deployment or existing application data.
Resources created by the test suite must be cleaned up safely without removing resources that existed before the test run.
Acceptance criteria
One scenario validates Redis connectivity from the running Nextcloud environment.
One scenario validates that the web layer can reach and serve the running Nextcloud instance.
Both scenarios reuse the test infrastructure from Add the first reusable smoke test for the current Nextcloud stack #49
The same local command runs the complete smoke-test suite.
Shared test helpers are reused where appropriate.
Failures return a non-zero test result with useful output.
Existing environments and persistent data are not modified or removed.
No GitHub Actions workflow is added as part of this issue.
Good first issue
Keep this focused on extending the existing smoke-test suite with Redis and web integration coverage.
If a scenario requires changing the runtime architecture or testing application behavior, ask for guidance instead of expanding the scope.
Goal
Expand the smoke-test suite created by #49 with additional scenarios for essential integrations of the current Nextcloud stack.
#49 creates the test foundation and verifies the minimum case: the stack starts and Nextcloud reaches an installed state.
This issue adds coverage for Redis and the web layer using the same test suite.
Scope
Reuse the test framework, setup, isolation, cleanup, and local test command introduced by #49.
Add two focused scenarios:
Do not create another test runner or a separate test environment.
Scenario: Redis integration
Verify that the Redis service used by the current stack is reachable from the running Nextcloud environment.
The test must validate the connection expected by the stack, not only that the Redis container itself is running.
Keep the scenario limited to basic connectivity. Do not test Redis features, performance, or failure recovery.
Scenario: web integration
Access Nextcloud through the web service defined by the current Compose stack.
Verify that the web layer can reach the application and return a valid HTTP response from the running Nextcloud instance.
Keep the scenario at the HTTP/runtime level. Browser automation and application workflows are outside this smoke-test suite.
Test suite reuse
The new scenarios must be part of the same smoke-test suite created by #49.
The same documented local command must run the complete suite.
Reuse shared setup, teardown, readiness, and diagnostic helpers where appropriate.
GitHub Actions is not part of this issue. CI integration will later execute the same test suite.
Isolation and cleanup
Keep the isolation guarantees established by #49.
The tests must not depend on an existing deployment or existing application data.
Resources created by the test suite must be cleaned up safely without removing resources that existed before the test run.
Acceptance criteria
Good first issue
Keep this focused on extending the existing smoke-test suite with Redis and web integration coverage.
If a scenario requires changing the runtime architecture or testing application behavior, ask for guidance instead of expanding the scope.