Perform an The record should be added Add/Update or updated to the database. transaction for each entity (e.g., Enforcement Actions, Penalties) Make modifications to The selected record should This test is necessary to the data in the source be updated with the data confirm that the State system is system. Regenerate modifications. correctly generating/referencing the record(s) and RCRAInfo keys. If this is not the records being done correctly, the record will be identified as a new record and added to RCRAInfo, rather than updating the existing record Perform a deletion of a The deleted record should This test is necessary to parent record in the be deleted in RCRAInfo. confirm that the State source State system system is not sending delete transactions for cascade deleted children records. Modify data element(s) The source State system This test case is only which RCRAInfo should identify this as a necessary if the State source considers to be a delete transaction for system allows editing of data primary key (e.g., RCRAInfo, as well as an elements which RCRAInfo Evaluation Date). add transaction for the considers to be primary keys. record. “new” Perform an add/update The State owned data This test may be necessary transaction on State should be added or updated only for those States that model data that is associated in RCRAInfo. Errors should cross ownership of data in their to EPA owned data not be raised by RCRAInfo source system. referencing IOR issues Delete a join record in The association between This test is necessary to a many to many items in the many to many confirm that the XML relationship (e.g. relationship, should be documents are being structured Compliance Schedule) removed but the individual properly and placing the delete entities should remain in transaction in the correct level RCRAInfo (e.g., Violations of the data hierarchy in the and Enforcement Action) schema Delete a primary The primary element should This test is necessary to element involved in a be deleted with the confirm that the XML many to many associated join record being documents are being structured relationship (e.g., cascade deleted by properly and placing the delete Enforcement) RCRAInfo transaction in the correct level of the data hierarchy in the schema Perform a full load of Verify key data points are It is recommended that prior to data correctly being loaded into initiating a full load of data a the system snapshot of data is obtained from RCRAInfo, to facilitate data verification. Whether the
Perform an Add/Update transaction for each entity (e.g., Enforcement Actions, Penalties) The record should be added or updated to the database. Make modifications to the data in the source system. Regenerate the record(s) and the records The selected record should be updated with the data modifications. This test is necessary to confirm that the State system is correctly generating/referencing RCRAInfo keys. If this is not being done correctly, the record will be identified as a new record and added to RCRAInfo, rather than updating the existing record Perform a deletion of a parent record in the State system The deleted record should be deleted in RCRAInfo. This test is necessary to confirm that the State source system is not sending delete transactions for cascade deleted children records. Modify data element(s) which RCRAInfo considers to be a primary key (e.g., Evaluation Date). The source State system should identify this as a delete transaction for RCRAInfo, as well as an add transaction for the “new” record. This test case is only necessary if the State source system allows editing of data elements which RCRAInfo considers to be primary keys. Perform an add/update transaction on State data that is associated to EPA owned data The State owned data should be added or updated in RCRAInfo. Errors should not be raised by RCRAInfo referencing IOR issues This test may be necessary only for those States that model cross ownership of data in their source system. Delete a join record in a many to many relationship (e.g. Compliance Schedule) The association between items in the many to many relationship, should be removed but the individual entities should remain in RCRAInfo (e.g., Violations and Enforcement Action) This test is necessary to confirm that the XML documents are being structured properly and placing the delete transaction in the correct level of the data hierarchy in the schema Delete a primary element involved in a many to many relationship (e.g., Enforcement) The primary element should be deleted with the associated join record being cascade deleted by RCRAInfo This test is necessary to confirm that the XML documents are being structured properly and placing the delete transaction in the correct level of the data hierarchy in the schema Perform a full load of data Verify key data points are correctly being loaded into the system It is recommended that prior to initiating a full load of data a snapshot of data is obtained from RCRAInfo, to facilitate data verification. Whether the
RCRA_FCD_v5.6.docx