@@ -285,12 +285,11 @@ \begin_layout Standard \begin_inset VSpace medskip \end_inset This document is believed to be acurate at the time of writing but as with - any opensource project the source code itself is the final arbiter of the - softwares behaviour. + any opensource project the source code itself is the reference. It is the responsibility of the end user to validate that the code will perform as they expect. The author assumes no responsibility for any inaccuracies that this document may contain. In no event will Matthew Welland be liable for direct, indirect, special, @@ -299,14 +298,14 @@ damages. \end_layout \begin_layout Standard -This document is a snapshot in time and the Megatest software has likely - been changed since publication. - This document and the product that it describes may be improved at any - time, without notice or obligation. +This document is a snapshot in time and Megatest software has likely changed + since publication. + This document and Megatest may be improved at any time, without notice + or obligation. \end_layout \begin_layout Standard \begin_inset Newpage newpage @@ -459,18 +458,17 @@ Megatest design philosophy \end_layout \begin_layout Standard Megatest is intended to provide the minimum needed resources to make writing - a suite of tests for software, design engineering or process control (via - owlfs for example) without being specialized for any specific problem space. + a suite of tests and implementing continuous build for software, design + engineering or process control (via owlfs for example) without being specialize +d for any specific problem space. Megatest in of itself does not know what constitutes a PASS or FAIL of a test. In most cases megatest is best used in conjunction with logpro or a similar tool to parse, analyze and decide on the test outcome. - A call to megatest can then be made to record the result. - \end_layout \begin_layout Subsection Megatest architecture \end_layout @@ -1675,10 +1673,23 @@ \end_layout \begin_layout Subsection Monitor logic \end_layout + +\begin_layout Standard +Note: The monitor is usable but incomplete as of Megatest v1.31. + Click on the +\begin_inset Quotes eld +\end_inset + +Monitor +\begin_inset Quotes erd +\end_inset + + button on the dashboard to start the monitor and give it a try. +\end_layout \begin_layout Standard \begin_inset Graphics filename monitor-state-diagram.svg @@ -1692,10 +1703,16 @@ \end_layout \begin_layout Subsection Configuration file Syntax \end_layout + +\begin_layout Standard +Note: whitespace is preserved including at the end of line. + Ensure your entries only have whitespace at the end of line when needed + to avoid problems. +\end_layout \begin_layout Subsubsection Sections \end_layout @@ -2008,11 +2025,11 @@ megatest.config \end_layout \begin_layout Standard \begin_inset Tabular - + @@ -2344,10 +2361,58 @@ \begin_layout Plain Layout \end_layout +\end_inset + + + + +\begin_inset Text + +\begin_layout Plain Layout +[jobgroups] +\end_layout + +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +string of letters, numbers and underscore +\end_layout + +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +number +\end_layout + +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +no +\end_layout + +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +Control number of jobs allowed to concurrently run in categories. + See [jobgroup] in testconfig +\end_layout + \end_inset @@ -2743,11 +2808,11 @@ testconfig file \end_layout \begin_layout Standard \begin_inset Tabular - + @@ -2894,54 +2959,150 @@ \end_inset - + +\begin_inset Text + +\begin_layout Plain Layout + +\end_layout + +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +jobgroup +\end_layout + +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout + +\end_layout + +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout + +\end_layout + +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout + +\end_layout + +\end_inset + + + + \begin_inset Text \begin_layout Plain Layout [items] \end_layout \end_inset - + \begin_inset Text \begin_layout Plain Layout any valid \end_layout \end_inset - + \begin_inset Text \begin_layout Plain Layout list of values \end_layout \end_inset - + +\begin_inset Text + +\begin_layout Plain Layout +no +\end_layout + +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +The test will be repeated once for each item with the variable name set + to the value. + If there is more than one variable then the test will be run against all + unique combinations of the values +\end_layout + +\end_inset + + + + +\begin_inset Text + +\begin_layout Plain Layout +[eztests] +\end_layout + +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +any valid +\end_layout + +\end_inset + + +\begin_inset Text + +\begin_layout Plain Layout +stepname command +\end_layout + +\end_inset + + \begin_inset Text \begin_layout Plain Layout no \end_layout \end_inset - + \begin_inset Text \begin_layout Plain Layout -The test will be repeated once for each item with the variable name set - to the value. - If there is more than one variable then the test will be run against all - unique combinations of the values +Use in addition to or instead of runscript for easy implementation of steps. + If .logpro exists it will be applied to the .log and + resulting exit code will be used to determine PASS/FAIL/WARN \end_layout \end_inset @@ -3870,11 +4031,11 @@ \begin_inset Text \begin_layout Plain Layout -If using logpro to asses the PASS/FAIL status of the step you specify the +If using logpro to acess the PASS/FAIL status of the step you specify the logpro file with this parameter. \end_layout \end_inset