Describe the bug
The repository currently contains two different types of tests:
- Core framework tests – Tests that validate internal Wheels framework functionality.
- Application tests – Tests intended for applications built using Wheels, not for testing the framework itself.
Application tests should typically remain empty (or minimal) in the framework repository because they are meant to be written by developers when they build their own Wheels applications.
However, there are currently tests present in the application tests directory that are actually testing core framework functionality.
To Reproduce
Steps to reproduce the behavior:
- Start a Wheels application.
- Click Tests in the navbar.
- You will see core tests written there.
Expected behavior
- Core framework functionality tests should be placed in the core test suite.
- Application tests should remain empty or only contain example tests relevant to a Wheels application.
Screenshots
Desktop:
- OS: macOS
- Wheels Branch: Develop
Additional context
Maintaining a clear separation between framework tests and application tests makes the test structure easier to understand for contributors and users of the framework.
Describe the bug
The repository currently contains two different types of tests:
Application tests should typically remain empty (or minimal) in the framework repository because they are meant to be written by developers when they build their own Wheels applications.
However, there are currently tests present in the application tests directory that are actually testing core framework functionality.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Screenshots
Desktop:
Additional context
Maintaining a clear separation between framework tests and application tests makes the test structure easier to understand for contributors and users of the framework.