Menu ▾ ▴

#64 PyTHIA: Tool to check consistency of applications before deployment ("preflight")

1.0
open
Yao Qian
None
2016-03-05
2015-07-30
David Suendermann-Oeft
No

Several recent discussions as well as the ticket

https://sourceforge.net/p/halef/tickets/55

suggests the creation of a tool which is to check the consistency of applications before deployment ("preflight"). The group consensus is to call this tool "PyTHIA", which stands for Python Testbench for HALEF Interactive Applications. This tool would check, e.g.:

  • the availability of prompts
  • the availability of grammars
  • the availability of TSV files
  • consistent naming schemes of variables (A_???, SC_???, etc., see https://sourceforge.net/p/halef/tickets/68/)
  • distinct naming of dialog states, see https://sourceforge.net/p/halef/tickets/68/
  • the fact whether a grammar file is in fact a grammar or something else (such as wav file, see https://sourceforge.net/p/halef/tickets/65)
  • the fact that there is a default transition out of every decision shape
  • whether there is a logical "IF" condition specified in the Branch shape for every action/semantic category that is specified in the preceeding script. (this was a callflow bug observed with the 7709 interview item, where the presence of one semantic category was not checked at all (typo), leading to going down the Default path whenever that semantic category was found)
  • the fact whether the script blocks were generated using the right GGS script (see e.g. Case https://sourceforge.net/p/halef/tickets/64/)
  • whether the right URL for the PHP logging scripts are used (again, whether the newest GGS scripts was used)
  • whether every question block is follwed by a script block
  • whether there are DTMF grammars specified (unless intended), since this may break stuff

Discussion

  • David Suendermann-Oeft

    David Suendermann-Oeft - 2015-08-04
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -9,3 +9,4 @@
 - the availability of TSV files
 - consistent naming schemes of variables (A_???, SC_???, etc.)
 - distinct naming of dialog states
+- the fact whether a grammar file is in fact a grammar or something else (such as wav file, see https://sourceforge.net/p/halef/tickets/65)
     

  • David Suendermann-Oeft

    David Suendermann-Oeft - 2015-08-04
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -10,3 +10,4 @@
 - consistent naming schemes of variables (A_???, SC_???, etc.)
 - distinct naming of dialog states
 - the fact whether a grammar file is in fact a grammar or something else (such as wav file, see https://sourceforge.net/p/halef/tickets/65)
+- the fact that there is a default transition out of every decision shape
     

  • David Suendermann-Oeft

    David Suendermann-Oeft - 2015-08-04
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -7,7 +7,7 @@
 - the availability of prompts
 - the availability of grammars
 - the availability of TSV files
-- consistent naming schemes of variables (A_???, SC_???, etc.)
-- distinct naming of dialog states
+- consistent naming schemes of variables (A_???, SC_???, etc., see https://sourceforge.net/p/halef/tickets/68/)
+- distinct naming of dialog states, see https://sourceforge.net/p/halef/tickets/68/
 - the fact whether a grammar file is in fact a grammar or something else (such as wav file, see https://sourceforge.net/p/halef/tickets/65)
 - the fact that there is a default transition out of every decision shape
     

  • Vikram Ramanarayanan

    Vikram Ramanarayanan - 2015-08-13
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -11,3 +11,4 @@
 - distinct naming of dialog states, see https://sourceforge.net/p/halef/tickets/68/
 - the fact whether a grammar file is in fact a grammar or something else (such as wav file, see https://sourceforge.net/p/halef/tickets/65)
 - the fact that there is a default transition out of every decision shape
+- whether there is a logical "IF" condition specified in the Branch shape for every action/semantic category that is specified in the preceeding script. (this was a callflow bug observed with the 7709 interview item, where the presence of one semantic category was not checked at all (typo), leading to going down the Default path whenever that semantic category was found)
     

  • Vikram Ramanarayanan

    Vikram Ramanarayanan - 2015-08-13
    • assigned_to: Vikram Ramanarayanan --> Yao Qian
     

  • Vikram Ramanarayanan

    Vikram Ramanarayanan - 2015-08-13
    • summary: Tool to check consistency of applications before deployment ("preflight") --> PyTHIA: Tool to check consistency of applications before deployment ("preflight")
     

  • Vikram Ramanarayanan

    Vikram Ramanarayanan - 2015-08-14
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -2,7 +2,7 @@

 https://sourceforge.net/p/halef/tickets/55

-suggests the creation of a tool which is to check the consistency of applications before deployment ("preflight").  This tool would check, e.g.:
+suggests the creation of a tool which is to check the consistency of applications before deployment ("preflight"). The group consensus is to call this tool "PyTHIA", which stands for Python Testbench for HALEF Interactive Applications. This tool would check, e.g.:

 - the availability of prompts
 - the availability of grammars
     

  • David Suendermann-Oeft

    David Suendermann-Oeft - 2015-08-19
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -12,3 +12,4 @@
 - the fact whether a grammar file is in fact a grammar or something else (such as wav file, see https://sourceforge.net/p/halef/tickets/65)
 - the fact that there is a default transition out of every decision shape
 - whether there is a logical "IF" condition specified in the Branch shape for every action/semantic category that is specified in the preceeding script. (this was a callflow bug observed with the 7709 interview item, where the presence of one semantic category was not checked at all (typo), leading to going down the Default path whenever that semantic category was found)
+- the fact whether the script blocks were generated using the right GGS script (see e.g. Case https://sourceforge.net/p/halef/tickets/64/)
     

  • David Suendermann-Oeft

    David Suendermann-Oeft - 2016-03-05
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -13,3 +13,6 @@
 - the fact that there is a default transition out of every decision shape
 - whether there is a logical "IF" condition specified in the Branch shape for every action/semantic category that is specified in the preceeding script. (this was a callflow bug observed with the 7709 interview item, where the presence of one semantic category was not checked at all (typo), leading to going down the Default path whenever that semantic category was found)
 - the fact whether the script blocks were generated using the right GGS script (see e.g. Case https://sourceforge.net/p/halef/tickets/64/)
+- whether the right URL for the PHP logging scripts are used (again, whether the newest GGS scripts was used)
+- whether every question block is follwed by a script block
+- whether there are DTMF grammars specified (unless intended), since this may break stuff
     

Log in to post a comment.

MongoDB Logo MongoDB
Gen AI apps are built with MongoDB Atlas
Atlas offers built-in vector search and global availability across 125+ regions. Start building AI apps faster, all in one place.
Try Free →