The technical requirements of the contest are fully described in the documents currently available on the website. It is recommended that all contestants thoroughly review the information prior to posting questions.
The contestant will need to interface with the databases associated with each VistA instance to demonstrate OS compatibility. The Step 1 test scenarios define a minimum set of configuration data for each VistA instance. An example script has been provided in the VMs on how to load configuration data into the instances for one of the test cases. The contestant is free to re-use or create new data for the VistA databases for both Step 1 and Step 2 testing.
For the contest scheduling software, the contestant is free to use any data model or create their own database in order to satisfy both Step 1 and Step 2 testing
Please clarify: "The contestant is free to re-use or create new data for the VistA databases for both Step 1 and Step 2 testing." Will any test data be pre-loaded on the VMs? For example, will test patients, providers, appointment types, stop codes, facilities, or other scheduling-related data be available in VMs provided by the VA? Or will the VistA’s provided on the VMs be presented as “clean slates”?
Of the three Virtual Machines provided to the contestant, only the Windows VISN-0 VM (also identified as the ca-xx..x VM) is preloaded with a limited set of patient data. The other VMs have no test data pre-loaded; however, Test Case 1 (provided in the VMs) contains procedures to load a limited set of test data into the system. Contestants are encouraged to use this set of data in their own test cases, and are welcome to extend or modify the provided scripts to give a database state sufficient for their own development and testing.
Having a couple issues to be ironed out with inability to access specific VM components via Remote. As a workaround until we can reach fluidity, we set up and are using a local test environment (expectations of less bugs with application module component(s) install and testing time on VM).
Unable to obtain the current VA specific Cache kit. Our emulator is using 64b Cache v.2011.1.2.701 Can you confirm that this is the Cache version closest to the one in current use by the VA and the VM enviroment? Thx David M.