Fix e2e test suite doc

[z1cheng]

What this PR does / why we need it:

Run ./hack/generate-e2e-suite-doc.sh > docs/e2e-tests.md to regenerate the doc.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• CVE Report (Scanner found CVE and adding report)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation only

Which issue/s this PR fixes

fixes #10395

How Has This Been Tested?

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I've read the CONTRIBUTION guide
• I have added unit and/or e2e tests to cover my changes.
• All new and existing tests passed.

[netlify]

✅ Deploy Preview for kubernetes-ingress-nginx ready!

Name	Link
🔨 Latest commit	fd13525
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-ingress-nginx/deploys/64fea870bc3fc6000842d666
😎 Deploy Preview	https://deploy-preview-10396--kubernetes-ingress-nginx.netlify.app/e2e-tests
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

Hi @z1cheng. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[z1cheng]

Some test cases still were not generated

[z1cheng]

Some test cases still were not generated, need to debug the script

/hold

[z1cheng]

Fix the script to:

1. ignore no Describe.* files
2. skip some basic framework files

/hold cancel

[tao12345666333]

https://kubernetes.github.io/ingress-nginx/e2e-tests/

it's working fine

[tao12345666333]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tao12345666333, z1cheng

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [tao12345666333]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[strongjz]

This is breaking for me now.....

./hack/generate-e2e-suite-doc.sh: line 24: /Users/strongjz/Documents/code/go/src/github.com/kubernetes/ingress-nginx/test/e2e/framework/framework.go: syntax error: operand expected (error token is "/Users/strongjz/Documents/code/go/src/github.com/kubernetes/ingress-nginx/test/e2e/framework/framework.go")
./hack/generate-e2e-suite-doc.sh: line 37: /Users/strongjz/Documents/code/go/src/github.com/kubernetes/ingress-nginx/test/e2e/metrics/metrics.go: syntax error: operand expected (error token is "/Users/strongjz/Documents/code/go/src/github.com/kubernetes/ingress-nginx/test/e2e/metrics/metrics.go")
2023-09-12T12:44:50+02:00 ERROR Could not run update hack script running "./hack/generate-e2e-suite-doc.sh " failed with exit code 1

[z1cheng]

Discussing it with @strongjz on Slack: https://kubernetes.slack.com/archives/C021E147ZA4/p1694523024439589