A computer-implemented method executed by one or more processors for testing of delivered software systems, the method comprising: receiving, by a data drive test (DDT) platform , one or more computer-readable files comprising test data, the test data comprising data to execute at least one transaction during testing of a software system that is at least partially hosted by a vendor back-end system (110; 204), the software system being configured for customer use; providing, by the DDT platform , one or more test scenarios for execution by the software system on the vendor back-end system (110; 204), the one or more test scenarios comprising a set of activities to conduct transactions by the software system using at least a portion of the test data; scheduling, by a scheduler of the DDT platform , execution of the one or more test scenarios using a test harness of the DDT platform to run on a periodic basis; executing, by the test harness of the DDT platform , the one or more test scenarios, wherein executing the one or more test scenarios at least partially comprises: converting, by the test harness , at least a portion of the test data from a first format to a second format; and transmitting, by the test harness , at least a portion of converted test data to the software system through one or more application programming interfaces (APIs) exposed by the vendor back-end system (110; 204); receiving, by the DDT platform , test results from the vendor back-end system (110; 204); comparing, by the DDT platform , the test results to expected results to provide a comparison as output; and providing, by the DDT platform , recommendations for future tests using test metrics and test metadata harvested from the testing of the software system. receiving, by a data drive test (DDT) platform , one or more computer-readable files comprising test data, the test data comprising data to execute at least one transaction during testing of a software system that is at least partially hosted by a vendor back-end system (110; 204), the software system being configured for customer use; providing, by the DDT platform , one or more test scenarios for execution by the software system on the vendor back-end system (110; 204), the one or more test scenarios comprising a set of activities to conduct transactions by the software system using at least a portion of the test data; scheduling, by a scheduler of the DDT platform , execution of the one or more test scenarios using a test harness of the DDT platform to run on a periodic basis; executing, by the test harness of the DDT platform , the one or more test scenarios, wherein executing the one or more test scenarios at least partially comprises: converting, by the test harness , at least a portion of the test data from a first format to a second format; and transmitting, by the test harness , at least a portion of converted test data to the software system through one or more application programming interfaces (APIs) exposed by the vendor back-end system (110; 204); converting, by the test harness , at least a portion of the test data from a first format to a second format; and transmitting, by the test harness , at least a portion of converted test data to the software system through one or more application programming interfaces (APIs) exposed by the vendor back-end system (110; 204); receiving, by the DDT platform , test results from the vendor back-end system (110; 204); comparing, by the DDT platform , the test results to expected results to provide a comparison as output; and providing, by the DDT platform , recommendations for future tests using test metrics and test metadata harvested from the testing of the software system. <EOS>