flagd/test/integration
renovate[bot] cd4604471b
chore(deps): update dependency go to v1.24.1 (#1559)
This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [go](https://go.dev/)
([source](https://redirect.github.com/golang/go)) | toolchain | minor |
`1.22.9` -> `1.24.1` |

---

### Release Notes

<details>
<summary>golang/go (go)</summary>

###
[`v1.24.1`](https://redirect.github.com/golang/go/compare/go1.24.0...go1.24.1)

###
[`v1.24.0`](https://redirect.github.com/golang/go/compare/go1.23.6...go1.24.0)

###
[`v1.23.7`](https://redirect.github.com/golang/go/compare/go1.23.6...go1.23.7)

###
[`v1.23.6`](https://redirect.github.com/golang/go/compare/go1.23.5...go1.23.6)

###
[`v1.23.5`](https://redirect.github.com/golang/go/compare/go1.23.4...go1.23.5)

###
[`v1.23.4`](https://redirect.github.com/golang/go/compare/go1.23.3...go1.23.4)

###
[`v1.23.3`](https://redirect.github.com/golang/go/compare/go1.23.2...go1.23.3)

###
[`v1.23.2`](https://redirect.github.com/golang/go/compare/go1.23.1...go1.23.2)

###
[`v1.23.1`](https://redirect.github.com/golang/go/compare/go1.23.0...go1.23.1)

###
[`v1.23.0`](https://redirect.github.com/golang/go/compare/go1.22.12...go1.23.0)

###
[`v1.22.12`](https://redirect.github.com/golang/go/compare/go1.22.11...go1.22.12)

###
[`v1.22.11`](https://redirect.github.com/golang/go/compare/go1.22.10...go1.22.11)

###
[`v1.22.10`](https://redirect.github.com/golang/go/compare/go1.22.9...go1.22.10)

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/open-feature/flagd).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xNjQuMSIsInVwZGF0ZWRJblZlciI6IjM5LjIwMC4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJyZW5vdmF0ZSJdfQ==-->

---------

Signed-off-by: Simon Schrottner <simon.schrottner@dynatrace.com>
Signed-off-by: Todd Baert <todd.baert@dynatrace.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Simon Schrottner <simon.schrottner@dynatrace.com>
Co-authored-by: Todd Baert <todd.baert@dynatrace.com>
2025-03-25 14:55:03 -04:00
..
config test: update e2e tests (#1452) 2024-11-19 16:22:39 -05:00
README.md chore: move e2e tests to test (#1005) 2023-11-15 09:27:40 -05:00
evaluation_test.go test: update e2e tests (#1452) 2024-11-19 16:22:39 -05:00
go.mod chore(deps): update dependency go to v1.24.1 (#1559) 2025-03-25 14:55:03 -04:00
go.sum chore(deps): update dependency go to v1.24.1 (#1559) 2025-03-25 14:55:03 -04:00
integration_test.go chore: move e2e tests to test (#1005) 2023-11-15 09:27:40 -05:00
json_evaluator_test.go test: update e2e tests (#1452) 2024-11-19 16:22:39 -05:00

README.md

Integration tests

The continuous integration runs a set of gherkin integration tests. If you'd like to run them locally, first pull the test-harness git submodule

git submodule update --init --recursive

then build the flagd binary

make build

then run the flagd binary

./bin/flagd start -f file:test-harness/symlink_testing-flags.json

and finally run

make integration-test

TLS

To run the integration tests against a flagd instance configured to use TLS, do the following:

Generate a cert and key in the repository root

openssl req -x509 -out localhost.crt -keyout localhost.key \
  -newkey rsa:2048 -nodes -sha256 \
  -subj '/CN=localhost' -extensions EXT -config <( \
   printf "[dn]\nCN=localhost\n[req]\ndistinguished_name = dn\n[EXT]\nsubjectAltName=DNS:localhost\nkeyUsage=digitalSignature\nextendedKeyUsage=serverAuth")

build the flagd binary

make build

then run the flagd binary with tls configuration

./bin/flagd start -f file:test-harness/symlink_testing-flags.json -c ./localhost.crt -k ./localhost.key

finally, either run the tests with an explicit path to the certificate:

make ARGS="-tls true -cert-path ./../../localhost.crt" integration-test

or, run without the path, defaulting to the host's root certificate authorities set (for this to work, the certificate must be registered and trusted in the host's system certificates)

make ARGS="-tls true" integration-test