Drop 'Testing Plan' section from dev design
Gerrit does have automated tests since a long time. We should probably have some dedicated documentation about how the Gerrit tests work so that contributors can learn how to write tests, but this information should not be part of the dev design. Hence just drop this useless section for now. Signed-off-by: Edwin Kempin <ekempin@google.com> Change-Id: I03e2c09c3b509b2d2cf212700845b9c6e6eb044e
This commit is contained in:
parent
bfa7a664cb
commit
885ed545d7
@ -640,15 +640,6 @@ logs may be mined for usage information. This is outside of the
|
||||
scope of Gerrit.
|
||||
|
||||
|
||||
== Testing Plan
|
||||
|
||||
Gerrit is currently manually tested through its web UI.
|
||||
|
||||
JGit has a fairly extensive automated unit test suite. Most new
|
||||
changes to JGit are rejected unless corresponding automated unit
|
||||
tests are included.
|
||||
|
||||
|
||||
== Caveats
|
||||
|
||||
Rietveld can't be used as it does not provide the "submit over the
|
||||
|
Loading…
x
Reference in New Issue
Block a user