Added a new FAQ

[Nandhini4501]

Added a new FAQ as per the ticket https://testsigma.atlassian.net/browse/DOC-413

Summary by CodeRabbit

• Documentation
  • Added FAQ guide explaining how the "Reset session for every test case" setting impacts automation test execution times and provides step-by-step instructions to optimize performance.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

A new FAQ documentation page added explaining how the "Reset session for every test case" setting extends automation test execution times. Includes front matter configuration and a seven-step resolution guide with visual references to disable per-test-case reset functionality.

Changes

Cohort / File(s)	Summary
FAQ Documentation src/pages/docs/FAQs/general/what-causes-longer-automation-test-execution-times-in-a-test-plan.md	New FAQ page added with front matter (title, meta description, order, page_id, warning, contextual links) and step-by-step resolution guide explaining the performance impact of per-test-case session resets

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify accuracy of the explanation regarding session reset behavior and execution time impact
• Validate step-by-step instructions are clear, accurate, and match current UI/product
• Confirm front matter metadata is correct (page_id, order, contextual links alignment)
• Check formatting consistency with existing FAQ documentation standards

Suggested reviewers

• bharathk08

Poem

🐰 A curious doc hops into view,
To show why resets make tests slow—true!
Seven steps to speed up the race,
Sessions now reset in the right place! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Added a new FAQ' is vague and generic, lacking specificity about which FAQ or what topic is being addressed.	Consider a more descriptive title that specifies the FAQ topic, such as 'Add FAQ on test execution times with per-test-case session reset' or similar.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch DOC-413

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 347bb83 and 6de65a1.

📒 Files selected for processing (1)

• src/pages/docs/FAQs/general/what-causes-longer-automation-test-execution-times-in-a-test-plan.md (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: CI

🔇 Additional comments (2)

src/pages/docs/FAQs/general/what-causes-longer-automation-test-execution-times-in-a-test-plan.md (2)

1-43: Clear documentation structure with well-organized resolution steps.

The FAQ is well-written with:

• Clear problem statement (line 17) explaining the performance impact
• Properly structured step-by-step resolution guide (lines 21–42)
• Consistent image references for visual guidance
• Appropriate metadata and contextual navigation links

The content effectively communicates the issue and resolution to users.

---

5-5: No issues to address. The page_id with trailing question mark (what-causes-longer-automation-test-execution-times-in-a-test-plan-?) follows the established convention in the documentation codebase for question-formatted FAQ titles. This pattern is used consistently across similar FAQ files and is intentional.

Likely an incorrect or invalid review comment.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}