Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
integration
Manage
Activity
Members
Labels
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Package Registry
Model registry
Operate
Terraform modules
Analyze
Contributor analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
elixxir
integration
Commits
3d523479
Commit
3d523479
authored
5 years ago
by
Bernardo Cardoso
Browse files
Options
Downloads
Patches
Plain Diff
Add more details about BasicE2E test to README
parent
310d0a03
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
basice2e/README.md
+22
-5
22 additions, 5 deletions
basice2e/README.md
with
22 additions
and
5 deletions
basice2e/README.md
+
22
−
5
View file @
3d523479
= Basic End-to-End Integration Test (basice2e)
This test runs several servers and clients as a smoke test against the
system. We run
s
a multi node, multi message, multi user test of the
system. We run a multi node, multi message, multi user test of the
system over multiple rounds all over network traffic. The basic
structure is as follows:
*
5 Nodes, BatchSize of 12
*
3 Clients, each send 4 messages over several rounds:
*
5 Nodes, BatchSize of 4
*
5 Gateways, each connected to its own node
*
User Discovery Bot
*
Channel Bot
*
Client sending 2 dummy messages per second, in order to fill batches
Then, the following tests are performed:
*
2 Clients (9 and 18) register with the system and UDB by Email
**
These users look each other up on UDB
**
Test is successful if the first line of gold output file matches
*
The same 2 clients exchange E2E encrypted messages for 65s at a rate of 0.1msg/s
**
This will result in clients sending 6 messages to each other
**
It will also test that 2 rekeys on each side happen properly
**
Test is successful if all the aforementioned messages are accounted for.
This is done by grep'ing the logs for sent messages, received messages, sent rekeys
and received rekeys, and comparing to gold output of 6, 6, 2, 2
*
4 Clients are started at two separate times and send messages to channel and to each other
**
2 messages to itself
**
1 message to each of the other nodes
*
Each client asserts they receive their predefined messages
**
1 message to each of the other clients
**
Test is successful if all gold output files match for client conversations:
4-5, 5-6, 6-7, 7-4
For now, we do nothing on assertion of crypto, we just assume
api-level compliance with sending and receiving messages.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment