Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
DiSL
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
5
Issues
5
List
Boards
Labels
Service Desk
Milestones
Merge Requests
1
Merge Requests
1
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Packages & Registries
Packages & Registries
Container Registry
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
DiSL
DiSL
Commits
90835ef7
Commit
90835ef7
authored
Oct 09, 2013
by
František Haas
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
fixed tests readme
parent
c6f513f4
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
6 deletions
+6
-6
README_TESTS
README_TESTS
+6
-6
No files found.
README_TESTS
View file @
90835ef7
...
...
@@ -2,22 +2,22 @@ Overview
========
Tests
are
implemented
using
JUnit
.
There
are
classic
unit
tests
that
are
located
in
the
ch
.
usi
.
dag
.
disl
.
test
2
.
junit
package
and
complex
tests
in
the
ch
.
usi
.
dag
.
disl
.
test
2
.
suite
package
that
invoke
all
parts
of
the
framework
located
in
the
ch
.
usi
.
dag
.
disl
.
test
.
junit
package
and
complex
tests
in
the
ch
.
usi
.
dag
.
disl
.
test
.
suite
package
that
invoke
all
parts
of
the
framework
(
client
,
server
,
...)
and
verify
computed
results
.
All
tests
are
performed
calling
-
ant
test
2
-
ant
test
To
use
the
for
debuging
purpose
during
development
a
single
suite
test
(
for
example
"after"
test
)
can
be
invoked
calling
-
ant
suite
-
test
2
-
Dtest2
.
name
=
after
-
ant
suite
-
test
-
Dtest
.
name
=
after
Parameters
specified
to
ant
at
command
line
starting
with
"-Ddisl."
are
passed
to
the
test
.
For
example
to
show
tests
output
specify
-
-
Ddisl
.
test
.
verbose
=
true
When
built
with
"ant prepare-test
2
"
tests
can
be
also
run
directly
.
They
are
When
built
with
"ant prepare-test"
tests
can
be
also
run
directly
.
They
are
packed
in
the
"build-test"
directory
.
...
...
@@ -27,7 +27,7 @@ Implementation
Implementation
is
a
bit
tricky
in
few
aspects
.
Firstly
,
building
of
suite
test
apps
and
instrumentations
is
handled
by
a
scripted
target
that
lists
all
directories
in
a
"ch.usi.dag.disl.test
2
.suite"
scripted
target
that
lists
all
directories
in
a
"ch.usi.dag.disl.test.suite"
package
and
one
by
one
"app"
and
"instr"
package
are
jared
.
Secondly
,
when
running
the
instances
of
client
and
server
using
Process
API
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment