Lines Matching refs:side

24 | client-side tests         | client/site_tests/      |
25 | server-side tests         | server/site_tests       |
68 Autotest has a notion of both client-side tests and server-side tests.  Code in
69 a client-side test runs only on the device under test (DUT), and as such isn’t
71 and the like.  If possible, an autotest should be written as a client-side
73 just like a client-side test.  It can use various autotest primitives (and
75 all, tests that use Servo or remote power management should be server-side
81 code, whether client-side test, server-side test, or library, have a strong
132 the host.  For a client-side test, “the host” means “the DUT”.  For a
133 server-side test, “the host” typically means “the system running autoserv”;
152 | WARN     | error.TestWarn    | error.TestWarn should be used when side effects to the test runnin…
158 ### Considerations when writing client-side tests
160 All client-side tests authored at Google must live in the client/site\_tests sub-directory of the a…
192 ### Considerations when writing server-side tests
194 All server-side tests authored at Google must live in the server/site\_tests
197 It should be even easier to keep the server-side of a test in pure python, as
200 ### When/why to write a server-side test
202 Server-side tests are appropriate when some operation in the test can't be
208 One simple criterion for whether to write a server-side test is this:  Is the
210 server-side test makes sense.
212 ### Control files for server-side tests
214 Server-side tests commonly operate on the DUT as an object.  Autotest
224 Below is a sample fragment for a control file that runs a simple server side test in parallel on al…
235 method of a server-side test defines an argument named host with a default
258 For server-side tests that use a servo-attached DUT, the host object has a
304 ### Calling client-side tests from a server-side test
306 Commonly, server-side tests need to do more on the DUT than simply run short
307 shell commands.  In those cases, a client-side test should be written and
308 invoked from the server-side test.  In particular, a client side test allows
309 the client side code to be written in Python that uses standard Autotest
312 Below is a short snippet showing the standard form for calling a client-side
313 test from server-side code:
339  * Used only in server-side tests: server/cros
340  * Used in both server- and client-side tests, or only client:
352 discussed above in Writing client-side tests.  If you’re writing the tool, and