[js] Delete tests and files which are not run any more

[shs96c]

PR Type

Tests

---

Description

• Remove unused JavaScript test files no longer executed

• Delete IE driver test HTML files and bootstrap script

• Clean up legacy Closure-based test infrastructure

• Remove test utilities and helper modules

---

Diagram Walkthrough

flowchart LR
  A["Unused JS Tests"] -->|Delete| B["test_bootstrap.js"]
  A -->|Delete| C["logging_test.js"]
  A -->|Delete| D["stacktrace_test.js"]
  A -->|Delete| E["testutil.js & testutil_test.js"]
  A -->|Delete| F["IE Driver HTML Tests"]

Loading

File Walkthrough

Relevant files

Tests

test_bootstrap.js Remove IE driver test bootstrap script                                      javascript/ie-driver/test/test_bootstrap.js Deleted entire bootstrap file that loaded WebDriver scripts Removed Closure Library debug loader initialization Removed script loading mechanism for test dependencies +0/-72    logging_test.js Remove logging module test file                                                    javascript/webdriver/test/logging_test.js Deleted complete test file for logging functionality Removed tests for LogRecord conversion and Preferences Removed Closure-based logging level tests +0/-85    stacktrace_test.js Remove stacktrace parsing test suite                                          javascript/webdriver/test/stacktrace_test.js Deleted comprehensive stacktrace parsing test suite Removed tests for V8, Firefox, IE10, and Closure stack frame parsing Removed error formatting and stack trace manipulation tests +0/-480  testutil.js Remove test utility module                                                              javascript/webdriver/test/testutil.js Deleted test utility module with helper functions Removed StubError class and callback helper utilities Removed promise assertion and callback pair management functions +0/-209  testutil_test.js Remove testutil test file                                                                javascript/webdriver/test/testutil_test.js Deleted test file for testutil module Removed tests for callback helper and callback pair functionality Removed assertion tests for callback execution +0/-102  get_element_rect_test.html Remove element rect test HTML                                                        javascript/ie-driver/test/get_element_rect_test.html Deleted HTML test file for element rectangle functionality Removed tests for getBoundingClientRect and non-integer coordinates Removed test HTML markup and styling +0/-73    locator_test.html Remove locator test HTML file                                                        javascript/ie-driver/test/locator_test.html Deleted HTML test file for element locator functionality Removed tests for className, XPath, and CSS selector validation Removed test DOM elements and form structures +0/-81    parent_overflow_test.html Remove parent overflow test HTML                                                  javascript/ie-driver/test/parent_overflow_test.html Deleted HTML test file for parent overflow detection Removed tests for scrollIntoView and overflow state checking Removed test DOM structure with scrollable container +0/-49

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.