This is especially important for any systems that might exist on the Internet and not on the Connectathon network. Needs to understand the profile documentation and the requirements for each actor in the profile. You may or may not find a condensed version of requirements that have been extracted in a table.
Assume that you will have to understand at a detailed level. Many Connectathon tests are document in the Gazelle Test Management system. This is by domain. Some domains manage test definitions outside of Gazelle.
Some of the tests need to be performed ahead of the connectathon and some need to be performed during the connectathon. All participants are required to run a series of software tests in advance of the Connectathon. These tests, typically done with tools provided by IHE, are designed as auditing tests to make sure you have prepared in advance; these are not full test suites or certification tests for a profile.
Each participant system is assigned a table that typically seats two people comfortably. A participant will select a test to be run, and Gazelle presents a list of test partners. After a specific test is completed, the participant marks the test complete in Gazelle.
This page is dedicated to the newbies but most of the tips apply to everybody so do not hesitate to go through this page. This is so important that it's basically the Golden Rule. We're all in it together and to be successful with our tests, we need each other.
Luckily, the Connectathon-floor is mostly "manager-and sales rep"-free, there are only helpful developers and there is a big camaraderie. Competition stops at the door.
Trying to be helpful is great, but you also have to be honest. If someone asks you to do a test and you really don't have time for it, just say no. Don't make someone else wait for you and waste his precious time. Everything starts at the specs Technical Framework.
Make sure your implementation is based on the most recent version, there's a new release about every year. Supplements are released even more often, so be sure to pay close attention to when new versions are released. The specs are carefully constructed by committees, so usually there is little room for interpretation. Most disputes at Connectathon you're doing it wrong! Although we try to make testing as easy as possible, this is not an easy task and discovering how the test tools are working on the connectathon floor is not a solution!
This should be pretty obvious, but what I'm trying to say is that when you're planning to re develop an implementation for the Connectathon, you should leave plenty of room to test your software before actually going.
0コメント