Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Tests end to end (e2e): add a app.base_path in opencti to cover more use case #8737

Open
aHenryJard opened this issue Oct 22, 2024 · 0 comments
Open

Tests end to end (e2e): add a app.base_path in opencti to cover more use case #8737

aHenryJard opened this issue Oct 22, 2024 · 0 comments
Labels
feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team test automation use to identify issue related to test automation implementation

Comments

@aHenryJard
Copy link
Member

Use case

I's quite easy to forgot to test or verify base_path on frontend feature, my proposal is to change drone CI and local CI for end to end to add a base path in order to cover that "without thinking".

Current Workaround

Manual testing on review.

Proposed Solution

Additional Information

If the feature request is approved, would you be willing to submit a PR?

Yes
@aHenryJard aHenryJard added feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team test automation use to identify issue related to test automation implementation labels Oct 22, 2024
@Kedae Kedae added good first issue TEMP : TEST and removed good first issue TEMP : TEST labels Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team test automation use to identify issue related to test automation implementation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aHenryJard @Kedae