File: test_instructions.md

package info (click to toggle)
chromium 139.0.7258.127-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 6,122,156 kB
  • sloc: cpp: 35,100,771; ansic: 7,163,530; javascript: 4,103,002; python: 1,436,920; asm: 946,517; xml: 746,709; pascal: 187,653; perl: 88,691; sh: 88,436; objc: 79,953; sql: 51,488; cs: 44,583; fortran: 24,137; makefile: 22,147; tcl: 15,277; php: 13,980; yacc: 8,984; ruby: 7,485; awk: 3,720; lisp: 3,096; lex: 1,327; ada: 727; jsp: 228; sed: 36
file content (45 lines) | stat: -rw-r--r-- 1,143 bytes parent folder | download | duplicates (6) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
 
# Testing Cronet native API on desktop

[TOC]

## Overview

The Cronet native API is cross-platform, usable on multiple desktop and mobile
platforms.

TODO(caraitto): Add mobile test information for the native API in the
Android page as instructions for testing vary by platform.

## Checkout and build

See instructions in the [common checkout and
build](/components/cronet/build_instructions.md).

## Running tests locally

To run Cronet native API unit and integration tests:

```shell
$ gn gen out/Default  # Generate Ninja build files.
$ autoninja -C out/Default cronet_unittests cronet_tests  # Build both test suites.
$ ./out/Default/cronet_unittests  # Run unit tests.
$ ./out/Default/cronet_tests  # Run the integration tests.
```

# Running tests remotely

To test against all tryjobs:

```shell
$ git cl upload  # Upload to Gerrit.
$ git cl try  # Run the tryjob, results posted in the Gerrit review.
```

This will test against several mobile and desktop platforms, along with
special configurations like ASAN and TSAN.

You can use the -b flag to test against just one of those, like this:

```shell
$ git cl try -b linux-rel
```