- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 128 for teststr (0.14 sec)
-
docs/en/docs/advanced/async-tests.md
│ └── test_main.py ``` The file `main.py` would have: ```Python {!../../../docs_src/async_tests/main.py!} ``` The file `test_main.py` would have the tests for `main.py`, it could look like this now: ```Python {!../../../docs_src/async_tests/test_main.py!} ``` ## Run it You can run your tests as usual via: <div class="termy"> ```console $ pytest ---> 100% ``` </div>
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Sat Jan 13 12:07:15 GMT 2024 - 3.9K bytes - Viewed (0) -
dbflute_fess/dfprop/sourceCopyright.dfprop
Plain Text - Registered: Mon May 06 08:04:11 GMT 2024 - Last Modified: Sat Oct 31 23:35:14 GMT 2015 - 344 bytes - Viewed (0) -
requirements-tests.txt
-e .[all] -r requirements-docs-tests.txt pytest >=7.1.3,<8.0.0 coverage[toml] >= 6.5.0,< 8.0 mypy ==1.8.0 ruff ==0.2.0 dirty-equals ==0.6.0 # TODO: once removing databases from tutorial, upgrade SQLAlchemy # probably when including SQLModel sqlalchemy >=1.3.18,<1.4.43 databases[sqlite] >=0.3.2,<0.7.0 flask >=1.1.2,<3.0.0 anyio[trio] >=3.2.1,<4.0.0 python-jose[cryptography] >=3.3.0,<4.0.0 pyyaml >=5.3.1,<7.0.0 passlib[bcrypt] >=1.7.2,<2.0.0
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Mon Apr 29 23:48:42 GMT 2024 - 496 bytes - Viewed (0) -
analysis/analysis-api-fir/build.gradle.kts
testImplementation(projectTests(":compiler:tests-common")) testApi(projectTests(":compiler:test-infrastructure-utils")) testApi(projectTests(":compiler:test-infrastructure")) testImplementation(projectTests(":compiler:tests-common-new")) testImplementation(projectTests(":compiler:fir:analysis-tests:legacy-fir-tests")) testImplementation(projectTests(":analysis:analysis-api-impl-base"))
Plain Text - Registered: Fri Apr 26 08:18:10 GMT 2024 - Last Modified: Fri Apr 05 16:42:25 GMT 2024 - 4.3K bytes - Viewed (0) -
docs/fr/docs/contributing.md
### Documentation pour les tests La plupart des tests sont en fait effectués par rapport aux exemples de fichiers sources dans la documentation. Cela permet de s'assurer que : * La documentation est à jour. * Les exemples de documentation peuvent être exécutés tels quels. * La plupart des fonctionnalités sont couvertes par la documentation, assurées par la couverture des tests.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Jul 27 18:51:07 GMT 2023 - 16.3K bytes - Viewed (0) -
build-logic/integration-testing/src/main/kotlin/gradlebuild.cross-version-tests.gradle.kts
group = "verification" description = "Runs the cross-version tests against all Gradle versions with 'forking' executer" } val quickFeedbackCrossVersionTests = tasks.register("quickFeedbackCrossVersionTests") { group = "verification" description = "Runs the cross-version tests against a subset of selected Gradle versions with 'forking' executer for quick feedback" }
Plain Text - Registered: Wed Mar 27 11:36:08 GMT 2024 - Last Modified: Sat Sep 30 16:17:28 GMT 2023 - 4.1K bytes - Viewed (0) -
CONTRIBUTING.md
**4. Approved** - Once the PR is approved, it gets `kokoro:force-run` label applied and it initiates CI/CD tests. - We can't move forward if these tests fail. - In such situations, we may request you to make further changes to your PR for the tests to pass. - Once the tests pass, we now bring all the code into the internal code base, using a job called "copybara".
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Thu Mar 21 11:45:51 GMT 2024 - 15.6K bytes - Viewed (0) -
docs/es/docs/deployment/versions.md
Para esto es recomendable primero añadir tests a tu aplicación. Con **FastAPI** es muy fácil (gracias a Starlette), revisa la documentación [Testing](../tutorial/testing.md){.internal-link target=_blank} Luego de tener los tests, puedes actualizar la versión de **FastAPI** a una más reciente y asegurarte de que tu código funciona correctamente ejecutando los tests.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Wed Feb 07 11:55:38 GMT 2024 - 4.2K bytes - Viewed (0) -
okhttp-hpacktests/README.md
OkHttp HPACK tests ================== These tests use the [hpack-test-case][1] project to validate OkHttp's HPACK implementation. The HPACK test cases are in a separate git submodule, so to initialize them, you must run: git submodule init git submodule update TODO ---- * Add maven goal to avoid manual call to git submodule init. * Make hpack-test-case update itself from git, and run new tests.
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Dec 15 16:59:53 GMT 2014 - 578 bytes - Viewed (0) -
misc/ios/README
To use the go tool to run individual programs and tests, put $GOROOT/bin into PATH to ensure the go_ios_$GOARCH_exec wrapper is found. For example, to run the archive/tar tests: export PATH=$GOROOT/bin:$PATH GOOS=ios GOARCH=amd64 CGO_ENABLED=1 go test archive/tar The go_ios_exec wrapper uses GOARCH to select the emulator (amd64) or the device (arm64). However, further setup is required to run tests or programs directly on a device.
Plain Text - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Tue Dec 29 21:49:26 GMT 2020 - 2.7K bytes - Viewed (0)