Differences

This shows you the differences between two versions of the page.

--- seqoutplugin [2016/09/22 02:36]
127.0.0.1 external edit
+++ — (current)
@@ Line 1: / Line 1: @@
-=====SeqOut Plugin=====
-//SeqOut Plugin// generates the test sequence from your model/mScript to an HTML webpage or Excel document.
-The format can be customized by editing the format property file //seqout.fmt// (see [[SeqOutFormat|SeqOutFormat]]) and XSL style sheet //seqout.xsl//. This plugin may require separate license.
-----
-====Usage====
-You must activate //SeqOut// plugin in [[ModelNode|ModelNode]]  before running the model.  There are two output formats available with this plugin: Excel and Web Page.  Select the right plugin format and execute the model.
-The output will be generated when the model execution is completed. Please be aware that this plugin does not actually connect to AUT.
-One issue you may encounter is that the graph generated for each test case may be too wide to fit in the page, which makes it difficult to print. This can be addressed by changing the graph orientation for the model from //Left/Right// to //Top/Down// in [[ModelNode|Model Property]].
-You may also double click on the graph to force the graph to resize to fit the entire width of the window.
-By default, sequence graph is generated to describe each test case.  You may change it to generate Message Sequence Chart (MSC) to describe the test case instead by selecting the corresponding format from the dropdown list field //Test Path Graph Type//.
-----
-==== Custom Output Format====
-This plugin serves similar purpose as //$seqout('text')// and //<seqout>// tags (see also [[TestCase Report File|TestCase Report File]]), which is used to generate test sequence to be used outside //TestOptimal// either for documentation purpose or offline testing using external test automation systems. However //SeqOut plugin// was created to quickly and conveniently generate test sequence from the model/mScript in human readable format for manual testing and documentation.
-See [[Default seqout.xsl Format|default test case format]].
-You may create as many custom formats as you need by creating a set of format property file and XSL style sheet file for each custom format and add them to the list of plugins (see instruction below).
-//TestOptimal// generates the test sequence using the formats defined in format file and saves the [[http://testoptimal.com/example/seqout.html.xml|output in xml format]] in //report// folder. It then calls [[http://testoptimal.com/example/seqout.xsl|seqout.xsl]] (or your custom xsl) transform xml data into the desired format.
-----
-====Configuration====
-After the custom format files are created, place them in /MbtSvr/config folder and define them to the system by adding the following row to the //Plugins// field in Help/Config page:
-    com.webmbt.plugin.SeqOutPlugin,SeqOutWeb,seqout.fmt,seqout.html,seqout.xsl;
-where //SeqOutWeb// is the plugin id you assign to the format, it is displayed in //Plugin// field in [[ModelNode|ModelNode]]. Note it must starts with //SeqOut//.
-//seqout.fmt// is the name of the format property file. This file contains formatting rules used by the plugin to generate output for each mScript method.
-//seqout.html// is the name of the output file to store the generated sequences. This argument is optional. If not supplied, the default value of seqout.html is used.
-//seqout.xsl// is the name of XSL style sheet file. This argument is optional. If not supplied, the default value of seqout.xsl is used.
-----
-====Customization====
-Do not make changes to the original //seqout.fmt// or //seqout.xsl// to avoid your changes being overridden by the software updates. If you need to customize these files, do so on the copy and change the plugin configuration to use the new file.
-----
-====Output to Excel====
-The test case is output to Excel workbook document with the following sheets:
-  - Model - contains model attributes and model execution parmaters
-  - Requirements - contains list of all requirements covered by the model
-  - TestCases - contains test cases generated and their steps with associated requirement tags