Current Status and Next Steps for Phoenix Editor Testing:
Parcel Testing: We've successfully updated unit tests to ensure the command dictionary functions correctly with the new parcel container. However, our current tests don't comprehensively cover the channel and parameter aspects of the expansion functionality. We need to expand our unit test suite to include thorough testing of these areas.
Database Testing: To ensure data integrity, we need to implement database tests that verify expected behavior during cascading deletions within the sequencing tables. For example, deleting a command dictionary should trigger the deletion of the associated parcel, but not the underlying expansion rule.
Checked for duplicates
Yes - I've already checked
Alternatives considered
Yes - and alternatives don't suffice
Related problems
No response
Describe the feature request
Current Status and Next Steps for Phoenix Editor Testing:
Parcel Testing: We've successfully updated unit tests to ensure the
commanddictionary functions correctly with the new parcel container. However, our current tests don't comprehensively cover thechannelandparameteraspects of the expansion functionality. We need to expand our unit test suite to include thorough testing of these areas.Database Testing: To ensure data integrity, we need to implement database tests that verify expected behavior during cascading deletions within the sequencing tables. For example, deleting a command dictionary should trigger the deletion of the associated parcel, but not the underlying expansion rule.