SharePoint Selenium Java Automation -- 2
Budget: ₹750 – ₹1,250 INR
I’m building a compact set of Selenium-based tests in Java that will run against an internal SharePoint Online site, all developed and executed from VS Code. The site authenticates with the classic username-and-password flow, so the script needs to log in programmatically before it begins its work. Once inside, the pages rely heavily on dynamic elements—menus that appear on hover, tables that redraw with AJAX, modal dialogs, and the like—so reliable waits, smart locators, and a clean Page Object pattern are essential.
Here’s what I need from you:
• A runnable Maven or Gradle project in Java 11+ that opens the SharePoint portal in Chrome, signs in with supplied credentials, and demonstrates interaction with several highly dynamic components (e.g., expanding a ribbon, filling a form that loads fields on demand, downloading or scraping a list item).
• Clear comments within the code plus a concise README that explains setup in VS Code, required extensions, and how to point the tests at a different tenant if needed.
• Robust synchronization: explicit waits, expected conditions, or FluentWait—not Thread.sleep.
• A simple configuration layer (properties or YAML) that lets me change credentials and URLs without touching source.
I’ll consider the work complete when I can clone the repo, update the config, press F5 in VS Code, and watch the script sign in, navigate, manipulate at least two dynamic elements, and exit cleanly without unhandled errors.
Here’s what I need from you:
• A runnable Maven or Gradle project in Java 11+ that opens the SharePoint portal in Chrome, signs in with supplied credentials, and demonstrates interaction with several highly dynamic components (e.g., expanding a ribbon, filling a form that loads fields on demand, downloading or scraping a list item).
• Clear comments within the code plus a concise README that explains setup in VS Code, required extensions, and how to point the tests at a different tenant if needed.
• Robust synchronization: explicit waits, expected conditions, or FluentWait—not Thread.sleep.
• A simple configuration layer (properties or YAML) that lets me change credentials and URLs without touching source.
I’ll consider the work complete when I can clone the repo, update the config, press F5 in VS Code, and watch the script sign in, navigate, manipulate at least two dynamic elements, and exit cleanly without unhandled errors.