package org.gradle;

import org.testng.annotations.Test;

import static org.testng.Assert.assertEquals;

public class Test1 extends AbstractTest {

    @Test
    public void shouldPass() {
        assertEquals(1, value);
    }

<module>
<source path="">
  <!-- Hack to keep collect from hiding collect.testing supersource: -->
  <exclude name="**/testing/**"/>
</source>

<!--
    We used to set this only for packages that had manual supersource. That
    worked everywhere that I know of except for one place: when running the GWT
    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same

// Package testing provides support for automated testing of Go ...
PACKAGE testing

IMPORTPATH
	testdata/testing

IMPORTS
	bytes
	flag
	fmt
	io
	os
	runtime
	runtime/pprof
	strconv
	strings
	time

FILENAMES
	testdata/benchmark.go
	testdata/example.go
	testdata/testing.go

FUNCTIONS
	// An internal function but exported because it is cross-package; ...

# Testing WebSockets

You can use the same `TestClient` to test WebSockets.

For this, you use the `TestClient` in a `with` statement, connecting to the WebSocket:

```Python hl_lines="27-31"
{!../../../docs_src/app_testing/tutorial002.py!}
```

!!! note

LeeeeT <******@****.***> 1680341164 +0300

为此，要在 `with` 语句中使用 `TestClient` 连接 WebSocket。

```Python hl_lines="27-31"
{!../../../docs_src/app_testing/tutorial002.py!}
```

!!! note "笔记"

	defer t.Stop()

	// If this test fails, we will either throw (when siftdownTimer detects
	// bad when on update), or other timers will hang (if the timer in a
	// heap is in a bad state). There is no reliable way to test this, but
	// we wait on a short timer here as a smoke test (alternatively, timers
	// in later tests may hang).
	<-After(25 * Millisecond)
}

var (

 * from the integration test's local maven repository.
 *
 * <p>Intended to verify that POMs published by Gradle can be consumed by Maven. Tests should
 * publish artifacts to {@link AbstractIntegrationSpec#mavenRepo} and then use the resolve exposed
 * by this fixture to run tests against those published artifacts.</p>
 */
@SelfType(AbstractIntegrationSpec.class)

testing-pyramid.png...

You could want to set up a different database for testing, rollback the data after the tests, pre-fill it with some testing data, etc.

The main idea is exactly the same you saw in that previous chapter.

## Add tests for the SQL app