webrtc/rtc_tools/rtcbot/README - Issue 2965593002: Move webrtc/{tools => rtc_tools}

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: webrtc/rtc_tools/rtcbot/README

Issue 2965593002: Move webrtc/{tools => rtc_tools} (Closed)

Patch Set: Adding back root changes Created 3 years, 5 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch

« no previous file with comments | « webrtc/rtc_tools/rtcbot/OWNERS ('k') | webrtc/rtc_tools/rtcbot/bot/api.js » ('j') | no next file with comments »

OLD	NEW
1 === RTCBot ===	1 === RTCBot ===

2 RTCBot is a framework to write tests that need to spawn multiple webrtc	2 RTCBot is a framework to write tests that need to spawn multiple webrtc

3 endpoints.	3 endpoints.

4	4

5 == Description ==	5 == Description ==

6 RTCBot is a framework that allows to write tests where logic runs on a single	6 RTCBot is a framework that allows to write tests where logic runs on a single

7 host that controls multiple endpoints ("bots"). It allows creating complex	7 host that controls multiple endpoints ("bots"). It allows creating complex

8 scenarios that would otherwise require non-trival signalling between multiple	8 scenarios that would otherwise require non-trival signalling between multiple

9 parties.	9 parties.

10	10

(...skipping 39 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
50 * Bot type is specified directly by the test.	50 * Bot type is specified directly by the test.

51	51

52 == Android ==	52 == Android ==

53 Before running test with Android one MUST forward the device port 8080 to the	53 Before running test with Android one MUST forward the device port 8080 to the

54 host machine. That is easy to achieve with chrome port forwarding tools.	54 host machine. That is easy to achieve with chrome port forwarding tools.

55 - Visit chrome://inspect/devices on the host machine.	55 - Visit chrome://inspect/devices on the host machine.

56 - Configure and enable port forwarding 8080 -> localhost:8080	56 - Configure and enable port forwarding 8080 -> localhost:8080

57 - Open chrome on you Android device before running test, and leave it	57 - Open chrome on you Android device before running test, and leave it

58 running until the end of test.	58 running until the end of test.

59 - Run your test.	59 - Run your test.

OLD	NEW