Run ginkgo test failed

[PaulChen79]

I'm trying to run ginkgo test with testkube and here is my config

apiVersion: tests.testkube.io/v3
kind: Test
metadata:
  labels:
    executor: ginkgo-executor
    test-type: ginkgo-test
  name: integration-test
  namespace: testkube
spec:
  content:
    repository:
      type: git
      authType: basic
      branch: main
      uri: uri
      path: test_cases/integration_test
      usernameSecret:
        key: GIT_USERNAME
        name: testkube
      tokenSecret:
        key: GIT_TOKEN
        name: testkube
    type: git
  executionRequest:
    argsMode: override
    variables:
      GinkgoParallel:
        name: GinkgoParallel
        type: basic
        valueFrom: {}
      GinkgoLabelFilter:
        name: GinkgoLabelFilter
        type: basic
        value: --label-filter=integration
  type: ginkgo/test

After I applied test and start run test, I got error message said:

executions contain failed on errors (error: process started with command: ginkgo, exited with code:1  error: exit status 1
output: Failed to compile invoice_svc_rpc_response_test:

go: cannot find main module, but found .git/config in /data/repo
	to create a module there, run:
	cd ../../.. && go mod init


Ginkgo ran 1 suite in 6.339924ms

Test Suite Failed
)

Is there any mistake in my kubernetes configuration?

My folder structure is as below:

repo
├── test_cases
│      └── integration_test
│               └── test.go
│  go.mod
│  go.sum

[PaulChen79]

Additionally, I put some args override variable in my test yaml config.

I found out that in FindGinkgoParams step, it will successfully parsed my variable

🌍 Setting Ginkgo parameters from variables
✅ Ginkgo parameters from variables set: map[GinkgoLabelFilter:--label-filter=integration GinkgoParallel: GinkgoRecursive:-r]

But when it go through BuildGinkgoArgs step, they all gone as below.

🌍 Building Ginkgo arguments from params
✅ Ginkgo arguments from params built: []

And then my default command became only ginkgo from ginkgo -r -p --randomize-all --randomize-suites --keep-going --trace --junit-report report.xml.

What I expected is replace -p to none, and add --label-filter=integration flag to original command but in vain.

Where can I see a more comprehensive explanation? Or can you provide me with a complete example configuration?

Thanks a lot.

[vsukhin]

when you provide a path, then Testkube does a parse checkout of this dir. eitther checkout the whole repo or move pkg files
you can fully redefine default command and arguments https://docs.testkube.io/articles/creating-tests#redefining-the-prebuilt-executor-command-and-arguments

[PaulChen79]

Hi @vsukhin

After following the instruction in document you provided, it change default command correctly.

Here is my setting yaml

apiVersion: tests.testkube.io/v3
kind: Test
metadata:
  labels:
    executor: ginkgo-executor
    test-type: ginkgo-test
  name: integration-test
  namespace: testkube
spec:
  content:
    repository:
      type: git
      authType: basic
      branch: main
      uri: my-uri
      path: test_cases/integration_test
      usernameSecret:
        key: GIT_USERNAME
        name: testkube
      tokenSecret:
        key: GIT_TOKEN
        name: testkube
    type: git
  executionRequest:
    args:
    - --label-filter=integration -r
    argsMode: override
    command:
    - ginkgo
  type: ginkgo/test

But as my first question that my folder structure is as below.

repo
├── test_cases
│      └── integration_test
│               └── test.go
│  go.mod
│  go.sum

If I don't provide folder path, it will say:

❌ Execution failed: process started with command: ginkgo, exited with code:1  error: exit status 1
output: ginkgo run failed
 Found no test suites

If I provide folder path that my tests are in, It will say

executions contain failed on errors (error: process started with command: ginkgo, exited with code:1  error: exit status 1
output: Failed to compile invoice_svc_rpc_response_test:

go: cannot find main module, but found .git/config in /data/repo
	to create a module there, run:
	cd ../../.. && go mod init


Ginkgo ran 1 suite in 6.339924ms

Test Suite Failed
)

Do I have to put test.go and my go.mod together? Or is there something wrong with my configuration?

I can successfully test on my local environment with this folder structure, but when it is on kubernetes it fails.

[vsukhin]

yes, put them together