API & Selenium Debugging Help
Budget: ₹600 – ₹1,500 INR
I’m midway through an automation suite that blends Java-based Selenium tests with a small set of REST calls, all opened daily in VS Code/Visual Studio. Most of the framework is in place, however a series of flaky tests are failing and I’ve traced the trouble to two spots:
• Selenium scripts – several page-object methods are throwing stale-element exceptions or returning empty values even though the DOM looks stable.
• REST helpers – whenever the UI flow calls our GET endpoints, the response body comes back empty, although manual Postman hits work fine, so something in the data retrieval chain is off.
I’ve already ruled out environment issues, so I need another set of eyes to comb through the existing code, locate the bottlenecks, and patch them without rewriting the whole framework.
Your task
1. With Video call help with debugging and write the code.
2. Identify and fix the Selenium timing / locator problems.
3. Step through the Java backend helpers to pinpoint why the response parsing drops data, then patch or refactor as needed.
Tech stack in play: Java 17, TestNG, Selenium 4, RestAssured, Maven, and typical CI hooks in GitHub Actions. If you have stronger tooling preferences (e.g., IntelliJ) that’s fine as long as the final fix compiles and all pipelines pass.
Deliverable
A merge-ready pull request showing green on the full test suite, plus a brief markdown summary of the fixes applied and any recommendations for future stability.
I’m ready to start as soon as you can slot this in; [Removed by Admin]
• Selenium scripts – several page-object methods are throwing stale-element exceptions or returning empty values even though the DOM looks stable.
• REST helpers – whenever the UI flow calls our GET endpoints, the response body comes back empty, although manual Postman hits work fine, so something in the data retrieval chain is off.
I’ve already ruled out environment issues, so I need another set of eyes to comb through the existing code, locate the bottlenecks, and patch them without rewriting the whole framework.
Your task
1. With Video call help with debugging and write the code.
2. Identify and fix the Selenium timing / locator problems.
3. Step through the Java backend helpers to pinpoint why the response parsing drops data, then patch or refactor as needed.
Tech stack in play: Java 17, TestNG, Selenium 4, RestAssured, Maven, and typical CI hooks in GitHub Actions. If you have stronger tooling preferences (e.g., IntelliJ) that’s fine as long as the final fix compiles and all pipelines pass.
Deliverable
A merge-ready pull request showing green on the full test suite, plus a brief markdown summary of the fixes applied and any recommendations for future stability.
I’m ready to start as soon as you can slot this in; [Removed by Admin]