1. All new methods need to be included in OcapAppDriverInterface and also an implementation provided in OcapAppDriver.
  2. Method signatures should only include "simple types" (Java primitives and Strings)
  3. All methods need to be synchronous. Asynchronous functionality (e.g. tuning) should have a "WaitFor" counterpart APIs to allow the user to decide if they'd like to turn the asynch functionality in synchronous by calling the WaitFor on a specific state or event.
  4. New methods should have javadoc method description.
  5. Added code should follow RI Coding Conventions.
  6. The new code should be tested by calling at least once via a bean shell script which is run as part of the level 3 script - OcapAppDriverTest.bsh
  7. Do NOT mention hn, dvr, hndvr, core etc as part of the function name. Example: For the HN related playback start function, it should be named as playbackStart() only and not hnPlaybackStart() or playbackHNStart().

NOTE:  If we encounter a situation and are tempted to violate these "rules", we need to stop and assess whether the functionality needs to be added to the framework or if the test requires functionality beyond what this simple framework provides. 

  • No labels