8000 changes for adding description in the single test run result page by nayanakto · Pull Request #2648 · akto-api-security/akto · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

changes for adding description in the single test run result page #2648

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.

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

Open
wants to merge 12 commits into
base: master
Choose a base branch
from

Conversation

nayanakto
Copy link
Contributor
@nayanakto nayanakto commented Jun 9, 2025

Summary
This PR adds a description column to test results across the Issues page and Single Test Run page. The changes fetch issue descriptions from TestingRunIssues and display them in the UI with tooltips for better context.

Changes
Backend (Java)

  • StartTestAction.java: Added issuesDescriptionMap field and prepareIssueDescriptionMap() method to map descriptions from TestingRunIssues to test results
  • Utils.java: Added mapIssueDescriptions() utility method to handle the mapping logic
  • IssuesAction.java: Enhanced fetchIssuesByStatusAndSummaryId() to include description in projections and added description mapping

Frontend (React/JavaScript)

-IssuesPage.jsx: Added issueDescription field to issue data structure

  • SingleTestRunPage.js: Updated API calls to receive and pass issuesDescriptionMap
  • transform.js (testing): Modified prepareTestRunResult() to accept description map and display descriptions in collapsible rows with tooltips
  • transform.js (issues): Added TooltipText component to display descriptions in issue tables

private Map<String, String> prepareIssueDescriptionMap(ObjectId latestTestingSummaryId,
List<TestingRunResult> testingRunResults) {

if (testingRunResults == null || testingRunResults.isEmpty()) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

move to utils/dao

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

which line you want in utils/dao?


Map<TestingIssuesId, TestingRunResult> idToResultMap = new HashMap<>();
for (TestingRunResult result : testingRunResults) {
TestingIssuesId id = new TestingIssuesId(result.getApiInfoKey(), TestErrorSource.AUTOMATED_TESTING, result.getTestSubType());
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

code written for creating handleRefreshTableCount, abstract that out and use here as well

Copy link
gitguardian bot commented Jul 2, 2025

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
16784794 Triggered Bearer Token ac7b043 apps/testing/src/test/java/com/akto/test_editor/execution/TestAutomatedAuth.java View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0