|
| 1 | +################################################################################ |
| 2 | +# Copyright (c) 2024 Oracle and/or its affiliates. |
| 3 | +# |
| 4 | +# The Universal Permissive License (UPL), Version 1.0 |
| 5 | +# |
| 6 | +# Subject to the condition set forth below, permission is hereby granted to any |
| 7 | +# person obtaining a copy of this software, associated documentation and/or data |
| 8 | +# (collectively the "Software"), free of charge and under any and all copyright |
| 9 | +# rights in the Software, and any and all patent rights owned or freely |
| 10 | +# licensable by each licensor hereunder covering either (i) the unmodified |
| 11 | +# Software as contributed to or provided by such licensor, or (ii) the Larger |
| 12 | +# Works (as defined below), to deal in both |
| 13 | +# |
| 14 | +# (a) the Software, and |
| 15 | +# (b) any piece of software and/or hardware listed in the lrgrwrks.txt file if |
| 16 | +# one is included with the Software (each a "Larger Work" to which the Software |
| 17 | +# is contributed by such licensors), |
| 18 | +# |
| 19 | +# without restriction, including without limitation the rights to copy, create |
| 20 | +# derivative works of, display, perform, and distribute the Software and make, |
| 21 | +# use, sell, offer for sale, import, export, have made, and have sold the |
| 22 | +# Software and the Larger Work(s), and to sublicense the foregoing rights on |
| 23 | +# either these or other terms. |
| 24 | +# |
| 25 | +# This license is subject to the following condition: |
| 26 | +# The above copyright notice and either this complete permission notice or at |
| 27 | +# a minimum a reference to the UPL must be included in all copies or |
| 28 | +# substantial portions of the Software. |
| 29 | +# |
| 30 | +# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR |
| 31 | +# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, |
| 32 | +# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE |
| 33 | +# AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER |
| 34 | +# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, |
| 35 | +# OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE |
| 36 | +# SOFTWARE. |
| 37 | +################################################################################ |
| 38 | + |
| 39 | +# This file provides examples of properties that configure tests in this |
| 40 | +# module. |
| 41 | +# |
| 42 | +# QUICK GUIDE TO RUNNING TESTS: |
| 43 | +# 1. Create a copy of this file named "test.properties": |
| 44 | +# cp example-test.properties test.properties |
| 45 | +# 2. In test.properties, replace example values with real values (the file is |
| 46 | +# .gitignore'd, so sensitive info won't be checked in to the repo) |
| 47 | +# 3. Comment out any lines for which a value can not be provided (tests are |
| 48 | +# skipped if no value is configured). |
| 49 | +# 4. mvn clean verify |
| 50 | +# |
| 51 | +# CONFIGURING TEST PROPERTIES |
| 52 | +# Test properties are read from a properties file by the TestProperties class. |
| 53 | +# The TestProperties class can be found in: |
| 54 | +# ojdbc-provider-common/src/testFixtures/java/oracle/jdbc/provider/TestProperties.java |
| 55 | +# The default behavior of TestProperties is to read a file named |
| 56 | +# "test.properties" in the current directory. A non-default location may be |
| 57 | +# specified as a JVM system property: |
| 58 | +# mvn clean verify -Doracle.jdbc.provider.TestProperties=/path/to/my-test.properties |
| 59 | +# |
| 60 | +# MAINTAINING THIS FILE |
| 61 | +# Project maintainers should add an example to this file anytime they write a |
| 62 | +# test which requires a new property. Not doing so will inflict pain and |
| 63 | +# suffering upon our fellow programmers, and will also lead to increased |
| 64 | +# maintenance costs. |
| 65 | +# |
| 66 | +# IGNORING UNCONFIGURED PROPERTIES |
| 67 | +# No test should cause a build failure due to an unconfigured property. |
| 68 | +# Using JUnit terminology: A test should "abort" rather than "fail" when a |
| 69 | +# property is not configured. This means that the test does not pass, but it |
| 70 | +# does not cause the build to fail either. |
| 71 | +# Methods of the TestProperties class will automatically abort a test if a |
| 72 | +# property is not configured. The org.junit.jupiter.api.Assumptions class may |
| 73 | +# also be used directly to abort a test. |
| 74 | +# There is NO environment in which ALL tests can be run. Some tests may |
| 75 | +# require authentication as a managed identity in an Azure VM, while other |
| 76 | +# tests require authentication as an instance principal in an OCI compute |
| 77 | +# instance; These environments are mutually exclusive. This is one reason why |
| 78 | +# tests can not fail the build if a required property is not set. |
| 79 | +# A more practical reason is that developers may not need to run all tests if |
| 80 | +# their changes are isolated to single module. For instance, a developer |
| 81 | +# working on an OCI provider should not need to set up an Azure tenancy to test |
| 82 | +# their changes. |
| 83 | + |
| 84 | +OBSERVABILITY_URL=<url> |
| 85 | +OBSERVABILITY_USERNAME=<username> |
| 86 | +OBSERVABILITY_PASSWORD=<password> |
0 commit comments