From 714f6aa97e0a0fda9b2c6e57da4b99ca8a035619 Mon Sep 17 00:00:00 2001 From: Punya Biswal Date: Mon, 24 Jan 2022 15:48:57 -0500 Subject: [PATCH] Remove internal/ prefix for integrationtest --- exporter/collector/integrationtests.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/exporter/collector/integrationtests.md b/exporter/collector/integrationtests.md index bbbd203c1..5b2126a6c 100644 --- a/exporter/collector/integrationtests.md +++ b/exporter/collector/integrationtests.md @@ -6,7 +6,7 @@ and compare requests against recorded expectation fixtures. Currently, these tes metrics. The fixtures are located in the [`testdata/fixtures`][fixtures] directory and registered in -[`internal/integrationtest/testcases.go`][testcases]. +[`integrationtest/testcases.go`][testcases]. ## Running Tests @@ -81,17 +81,17 @@ To add a new test: This is how the Ops Agent fixtures were generated. -1. Add an entry in [`internal/integrationtest/testcases.go`][testcases]. +1. Add an entry in [`integrationtest/testcases.go`][testcases]. 1. Run the script to record the expectation fixture. This will contain the expected requests that the exporter makes to GCP services: ```sh - cd internal/integrationtest + cd integrationtest go run cmd/recordfixtures/main.go ``` The generated file is a JSON encoded - [`MetricExpectFixture`](internal/integrationtest/fixtures.proto#L21) protobuf message. + [`MetricExpectFixture`](integrationtest/fixtures.proto#L21) protobuf message. See [#229](https://github.com/GoogleCloudPlatform/opentelemetry-operations-go/pull/229) for an example PR. @@ -107,4 +107,4 @@ If you need to see the build logs because tests are failing, just ask someone to with you. [fixtures]: testdata/fixtures -[testcases]: internal/integrationtest/testcases.go +[testcases]: integrationtest/testcases.go