31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
|
along with Megatest. If not, see <http://www.gnu.org/licenses/>.
----------------------------
Why Megatest?
-------------
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
--------------------------
Megatest is a distributed system intended to provide the minimum needed
resources to make writing a suite of tests and tasks for implementing
continuous build for software, design engineering or process control (via
|
<
|
|
>
|
|
|
<
<
|
<
|
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
|
along with Megatest. If not, see <http://www.gnu.org/licenses/>.
----------------------------
Why Megatest?
-------------
Megatest was created to provide a generalized tool for managing suites
of regression tests and to provide a multi-host, distributed
alternative to "make". The EDA world is littered with proprietory,
company-specific tools for this purpose and by going open source and
keeping the tool flexible the hope is that Megatest could be useful to
any team at any company for continuous integration and almost any
other general automation tasks.
Megatest Design Philosophy
--------------------------
Megatest is a distributed system intended to provide the minimum needed
resources to make writing a suite of tests and tasks for implementing
continuous build for software, design engineering or process control (via
|
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
|
Tests are launched using the launching system available for the
distributed compute platform in use. A template script is provided
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[]
// :leveloffset: 0
include::writing_tests.txt[]
include::howto.txt[]
include::reference.txt[]
include::testplan.txt[]
|
>
>
|
|
|
|
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
|
Tests are launched using the launching system available for the
distributed compute platform in use. A template script is provided
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.
// :leveloffset: 0
include::overview.txt[]
include::plan.txt[]
include::installation.txt[]
include::getting_started.txt[]
include::study_plan.txt[]
include::writing_tests.txt[]
include::debugging.txt[]
include::howto.txt[]
include::reference.txt[]
include::testplan.txt[]
|