Quick Candidate Guide: Selenium Automation Project Assessment on DoSelect

Welcome! This guide will help you confidently navigate and complete your Selenium automation project on the DoSelect platform.

Please read it before starting your attempt to avoid mistakes and understand the tools provided.

Overview: What This Assessment Is About

You are given a project-based automation problem that requires writing Selenium logic in Java to interact with a dummy website (hosted locally within the platform). Your goal is to:

• Understand the problem requirements
  
  

• Interact with a form or web page using Selenium
  
  

• Implement logic in a specific method
  

• Pass automated test cases for evaluation
  

What You Will See on the Platform

A. Problem Description Panel

This panel appears on the left side when you open the assessment. It includes:

• Title & Tags: Indicate what kind of project it is (e.g., Selenium, Java, Automation).
  
  

• Overview: A summary of the use case you'll automate (e.g., form submission, data validation).
  
  

• Your Task: Step-by-step instructions on what your Selenium code should do.
  
  

• Constraints: Rules to follow (e.g., use specific selectors, handle errors gracefully).
  
  

• Expected Behaviour: High-level example of the end outcome.
  
  

 Carefully read the entire problem description before writing any code.

B. Project-Based IDE

You’ll work in an integrated development environment (IDE) similar to VS Code.

The IDE has:

• File Explorer on the left
  
  

• Editor window in the center
  
  

• Terminal and Test Output Tabs at the bottom
  
  

Run menu buttons at the top toolbar

C. Default Open Files

When the assessment loads, certain files will open by default:

• Editable Java File: Where you will write your Selenium logic. This is the only file you are allowed to modify.
  
  

HTML Files (Read-Only): Represent the website structure. Useful to understand field names and layout.

D. README Tab

This tab provides structured instructions about the project, including:

• The task summary
  
  

• Important file paths
  
  

• Behaviour expectations
  
  

• Rules and constraints
  
  

• How to run and test your code
  
  

• Testing flow and scoring logic
  
  

 Think of this as your rule book — refer to it throughout the assessment.

Navigating the Run Menu

At the top of the IDE, you'll see predefined buttons under the "Run" menu. These help you interact with the project easily:

Install Packages & Build

• Installs necessary dependencies and builds the project.
  
  

• Use this if you're starting fresh or want to reset your environment.
  
  

View Website Preview

• Starts a local preview server that lets you view the dummy web page (form, UI, etc.).
  
  

• Useful to visually inspect how the form behaves or what elements are present.
  
  

• Opens a preview tab at the bottom or side of the IDE.
  
  

⚠️ Do not use browser Inspect/DevTools — doing so may trigger proctoring flags.

Run Test Cases

• Executes a set of pre-written test cases that check if your Selenium logic works as expected.
  

• Opens logs and test result tabs showing which tests passed or failed.

File Types You’ll See

Editable File

• A single Java class file will be editable.
  
  

• It contains the method(s) where you are expected to write your logic.
  
  

Read-Only Files

• Website files (website/)
   HTML/CSS/JS for the dummy site. These help you understand the page, but cannot be edited.
  
  

• Test files (src/test/)
   Contains unit test logic. Use them to understand what cases will be tested.
  
  

Configuration files
 Like pom.xml, configuration.json is used by the system. Do not modify them.

Understanding the Test Results

After clicking Run Test Cases from the bottom right corner, two tabs will open:

Logs Tab

• Shows terminal output
  
  

• Useful for debugging (e.g., errors, exceptions)
  
  

Evaluation Details Tab

• Lists all test cases and whether they passed or failed
  
  

Provides a summary score

Scoring Explained

Each test case has a specific weight, defined internally. Your total score depends on how many test cases pass and how much each is worth.

Test Result Types:

• Accepted: All test cases passed → Full marks
  
  

• Partially Accepted: Some test cases passed → Partial marks
  
  

Failed: All test cases failed → Zero score

Submission Process

Once you’re satisfied with your solution:

• All test cases should pass (or as many as possible)
  
  

• Ensure you haven’t changed any read-only files
  
  

• Click the Submit button on the top right
  
  

⚠️ Submissions are final. Make sure to validate everything before you submit.

Platform Environment (Pre-Configured)

The platform is pre-set up. No need to install or configure anything.

• Java 11
  
  

• Maven 3.x
  
  

• Selenium HtmlUnitDriver (for headless testing)
  
  

 Ensure your logic works in a headless environment. There’s no browser UI in actual tests.

Important Best Practices

 ✅ Read the README and problem statement carefully
 ✅ Use only the provided method to implement logic
 ✅ Use field names exactly as mentioned
 ✅ Use selectors wisely — no hardcoding
 ✅ Handle errors properly — return the default value if needed
 ✅ Preview the website to understand the flow
 ✅ Check test names in the test files — they hint at what's being validated
 ✅ Run tests often to catch issues early
 ✅ Submit only when you're sure

Common Mistakes to Avoid

 ❌ Modifying read-only files
 ❌ Skipping the problem description or README
 ❌ Using hardcoded field names or values
 ❌ Leaving unhandled exceptions
 ❌ Submitting without running all tests
 ❌ Using Inspect Tool in website preview

Before You Start Checklist

 ✔ Read the problem description
✔ Read the README.md
✔ Explore open files and understand what’s editable
✔ Use website preview to understand UI
✔ Plan your logic before you code
 ✔ Use test case output to iterate and improve

You're all set to begin! Stay focused, follow the structure, and test your code carefully.
Good luck!