8000 Testing Strategy (question) · Issue #4 · 3l-gee/delorean · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Testing Strategy (question) #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
3l-gee opened this issue Mar 23, 2025 · 0 comments
Open

Testing Strategy (question) #4

3l-gee opened this issue Mar 23, 2025 · 0 comments
Assignees
Labels
question Further information is requested

Comments

@3l-gee
Copy link
Owner
3l-gee commented Mar 23, 2025

To ensure that Delorean works correctly and continues to function as expected, it must be thoroughly tested and controlled. While we aim to verify that the entire application operates as intended, we must focus on specific critical areas:

  • Loading AIXM datasets
  • Extracting AIXM datasets
  • Visualizing AIXM datasets
  • Generating AIXM datasets
  • Filtering AIXM datasets

These tests must ensure that the functionality is:

  • Complete – covering all necessary aspects
  • Robust – handling edge cases and unexpected inputs
  • Correct – producing accurate and expected results

To achieve this, tests should verify that all reasonable legal possibilities are allowed while ensuring that all reasonable illegal possibilities are prevented.
By reasonable, we refer to the different logical possibilities that lead to expected, distinct outcomes. For example, if a field is supposed to accept numbers that are only used for display purposes (i.e., the number itself serves no functional role), it would be reasonable to test values such as:

1, 0.1, 100

Additionally, we might test values such as:

AB, #

to create illegal cases that should be properly rejected.

Technical approach

The generic approach will be to craft sepecifi AIXM datasets that have alle the fields filled in and control against the database content between what is expected and what was loaded. TBH

@3l-gee 3l-gee self-assigned this Mar 23, 2025
@3l-gee 3l-gee added the question Further information is requested label Mar 23, 2025
@3l-gee 3l-gee pinned this issue Mar 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant
0