1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
|
The Megatest Users Manual
=========================
Matt Welland <matt@kiatoa.com>
v1.0, April 2012
:doctype: book
[preface]
Preface
-------
This book is organised as three sub-books; getting started, writing tests and reference.
.License
----------------------------
Copyright 2006-2017, Matthew Welland.
This document is part of Megatest.
Megatest is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
|
|
|
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
|
The Megatest Users Manual
=========================
Matt Welland <matt@kiatoa.com>
v1.5, June 2020
:doctype: book
[preface]
Preface
-------
This book is organised as three sub-books; getting started, writing tests and reference.
.License
----------------------------
Copyright 2006-2020, Matthew Welland.
This document is part of Megatest.
Megatest is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
|
| ︙ | | | ︙ | |
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
|
-------------
The Megatest project was started for two reasons, the first was an
immediate and pressing need for a generalized tool to manage a suite
of regression tests and the second was the fact that I had written or
maintained several such tools at different companies over the years. I
thought a single open source tool, flexible enough to meet the needs
of any team doing continuous integrating and or running a complex
suite of tests for release qualification would solve some problems for
me and for others.
-- Matt Welland, original author of the Megatest tool suite.
Megatest Design Philosophy
--------------------------
|
|
|
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
|
-------------
The Megatest project was started for two reasons, the first was an
immediate and pressing need for a generalized tool to manage a suite
of regression tests and the second was the fact that I had written or
maintained several such tools at different companies over the years. I
thought a single open source tool, flexible enough to meet the needs
of any team doing continuous integration and or running a complex
suite of tests for release qualification would solve some problems for
me and for others.
-- Matt Welland, original author of the Megatest tool suite.
Megatest Design Philosophy
--------------------------
|
| ︙ | | | ︙ | |
98
99
100
101
102
103
104
105
106
107
108
109
110
111
|
which can launch jobs on local and remote Linux hosts. Currently
megatest uses the network filesystem to call home to your master
sqlite3 database. Megatest has been used with the Intel Netbatch and
lsf (also known as openlava) batch systems and it should be
straightforward to use it with other similar systems.
include::overview.txt[]
include::installation.txt[]
include::getting_started.txt[]
include::study_plan.txt[]
|
>
>
|
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
|
which can launch jobs on local and remote Linux hosts. Currently
megatest uses the network filesystem to call home to your master
sqlite3 database. Megatest has been used with the Intel Netbatch and
lsf (also known as openlava) batch systems and it should be
straightforward to use it with other similar systems.
include::overview.txt[]
include::plan.txt[]
include::installation.txt[]
include::getting_started.txt[]
include::study_plan.txt[]
|
| ︙ | | | ︙ | |
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
|
------------------
["graphviz", "server.png"]
----------------------------------------------------------------------
include::server.dot[]
----------------------------------------------------------------------
include::plan.txt[]
// to allow the getting_started.txt to be a stand-alone document use level
shifting, note that the preceding blank line is needed.
// :leveloffset: 2
// [appendix]
// Example Appendix
// ================
// One or more optional appendixes go here at section level zero.
|
|
|
|
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
|
------------------
["graphviz", "server.png"]
----------------------------------------------------------------------
include::server.dot[]
----------------------------------------------------------------------
// include::plan.txt[]
// to allow the getting_started.txt to be a stand-alone document use level
// shifting, note that the preceding blank line is needed.
// :leveloffset: 2
// [appendix]
// Example Appendix
// ================
// One or more optional appendixes go here at section level zero.
|
| ︙ | | | ︙ | |