You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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:
These tests must ensure that the functionality is:
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
The text was updated successfully, but these errors were encountered: