Megatest

Check-in [a374d9084b]
Login
Overview
Comment:Updated manual
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | v1.65-broken
Files: files | file ages | folders
SHA1: a374d9084bb19e0715a3981a05f81b259a7500fc
User & Date: mrwellan on 2020-04-27 22:00:40
Other Links: branch diff | manifest | tags
Context
2020-04-28
11:36
Added fix for case where rmt calls returns a non list and a for-each crashes. check-in: ea8c3e52e9 user: mrwellan tags: v1.65-broken
2020-04-27
22:00
Updated manual check-in: a374d9084b user: mrwellan tags: v1.65-broken
20:32
Added some basic documentation of archive for save and get data check-in: 07ff7dca1e user: mrwellan tags: v1.65-broken
Changes

Modified docs/manual/megatest_manual.html from [c05cd0c27b] to [dd1dac404b].

2380
2381
2382
2383
2384
2385
2386



















2387
2388
2389
2390
2391
2392
2393
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412







+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+







</div></div>
<div class="paragraph"><p>To transfer the environment to the next step you can do the following:</p></div>
<div class="listingblock">
<div class="title">Propagate environment to next step</div>
<div class="content monospaced">
<pre>$MT_MEGATEST -env2file .ezsteps/${stepname}</pre>
</div></div>
</div>
<div class="sect2">
<h3 id="_scripts">Scripts</h3>
<div class="listingblock">
<div class="title">Specifying scripts inline (best used for only simple scripts)</div>
<div class="content monospaced">
<pre>[scripts]
loaddb #!/bin/bash
  sqlite3 $1 &lt;&lt;EOF
  .mode tabs
  .import $2 data
  .q
  EOF</pre>
</div></div>
<div class="paragraph"><p>The above snippet results in the creation of an executable script
called "loaddb" in the test directory. NOTE: every line in the script
must be prefixed with the exact same number of spaces. Lines beginning
with a # will not work as expected. Currently you cannot indent
intermediate lines.</p></div>
<div class="listingblock">
<div class="title">Full example with ezsteps, logpro rules, scripts etc.</div>
<div class="content monospaced">
<pre># You can include a common file
#
[include #{getenv MT_RUN_AREA_HOME}/global-testconfig.inc]

Modified docs/manual/reference.txt from [41ce966733] to [332bf8caed].

462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
462
463
464
465
466
467
468

469
470

471
472
473
474
475
476
477







-


-







--------------


Complex mapping example
~~~~~~~~~~~~~~~~~~~~~~~



// image::itemmap.png[]
image::complex-itemmap.png[]


We accomplish this by configuring the testconfigs of our tests C D and E as follows:

.Testconfig for Test E has
----------------------
[requirements]
waiton C
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
510
511
512
513
514
515
516




517
518
519
520
521
522
523







-
-
-
-







. Test A has no waitons.  All waitons of all tests in full list have been processed.  Full list is finalized.



itemstable
~~~~~~~~~~
An alternative to defining items is the itemstable section.  This lets you define the itempath in a table format rather than specifying components and relying on getting all permutations of those components.





Dynamic Flow Dependency Tree
~~~~~~~~~~~~~~~~~~~~~~~~~~~~

.Autogeneration waiton list for dynamic flow dependency trees
-------------------
[requirements]
650
651
652
653
654
655
656




















657
658
659
660
661
662
663
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677







+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+







To transfer the environment to the next step you can do the following:

.Propagate environment to next step
----------------------------
$MT_MEGATEST -env2file .ezsteps/${stepname}	  
----------------------------

Scripts
~~~~~~~

.Specifying scripts inline (best used for only simple scripts)
----------------------------
[scripts]
loaddb #!/bin/bash
  sqlite3 $1 <<EOF
  .mode tabs
  .import $2 data
  .q
  EOF
----------------------------

The above snippet results in the creation of an executable script
called "loaddb" in the test directory. NOTE: every line in the script
must be prefixed with the exact same number of spaces. Lines beginning
with a # will not work as expected. Currently you cannot indent
intermediate lines.

.Full example with ezsteps, logpro rules, scripts etc.
-----------------
# You can include a common file
#
[include #{getenv MT_RUN_AREA_HOME}/global-testconfig.inc]

# Use "var" for a scratch pad