Versions Compared

Old Version 6

changes.mady.by.user Nicolas Metts

Saved on

compared with

New Version Current

changes.mady.by.user Nicolas Metts

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

  1. Level 3 scripts can only call Level 2 scripts (example would be the smoke test bean shell script), no OCAP API calls or OcapAppDriver method calls.  
  2. Level 2 scripts can only call Level 1 scripts (example would be a sequence of menu option selections using DvrExerciser to perform an integration test).  Level 2 scripts can not call OCAP App Driver functions or OCAP APIs. 
  3. Level 1 scripts can only call OcapAppDriver functions (example would be "make a recording" bean shell script).  Level 1 scripts can not call other scripts or OCAP APIs.
  4. If a script needs to call an OCAP API which is not currently supported via OcapAppDriver API, a OcapAppDriver API should be added, see "How to Add A New Function" Design Documentation|../../../../../../../../../pages/viewpage.action?pageId=39846061|\
  5. Scripts should be checked into svn: trunk\ri\RI_Stack\apps\qa\org\cablelabs\lib\rxscripts into the appropriate subdirectory - level1, level2 or level3
  6. Level 3 script is responsible for setting the rxReturn and rxReturnString to report the overall status of the level 3 test script
  7. Level 1 and Level 2 scripts should return a String.  If the string is empty, this implies the script ran without problems and should be considered "PASS".  If the string is not empty, this implies the script ran into problems and should be considered "FAIL" with details provide in the returned string.
  8. Wiki Markup In Level 2  In Level 2 scripts, there should be a single "\[name of the script\]" method which will be used to call the script from Level 3 or other Level 2 scripts.  If more than one is needed, the script should be divided into more than one  If more than one is needed, the script should be divided into more than one script.
  9. rxLog() statements do not need to include a logging guard since the RiScriptlet does this on behalf of the script.
  10. rxLog() statements will start with the name of the bean shell script to help clarify log messages.  The RIScriptlet appends the name of the script to the log message automatically.
  11. If a script has methods within the file, the methods should have a prefix which is an abbreviation of the script file name, i.e. LiveStreamingTrick10 has a method call lst_subtest10()
  12. Although the scripts are not technically java, they should adhere to the RI coding standards, specifically to java standards where applicable.