0% found this document useful (0 votes)
26 views3 pages

SDET Interview Assignment - Homepage

The SDET interview assignment requires candidates to create a comprehensive testing strategy for the Analytics Vidhya webpage as an external black-box tester. Deliverables include a test strategy document, detailed test cases, optional bug reports, and mandatory automation samples using specified tools. The assignment is expected to take 6-8 hours and must be submitted within 72 hours, with evaluation based on strategy clarity, test case quality, edge case consideration, and code documentation.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
26 views3 pages

SDET Interview Assignment - Homepage

The SDET interview assignment requires candidates to create a comprehensive testing strategy for the Analytics Vidhya webpage as an external black-box tester. Deliverables include a test strategy document, detailed test cases, optional bug reports, and mandatory automation samples using specified tools. The assignment is expected to take 6-8 hours and must be submitted within 72 hours, with evaluation based on strategy clarity, test case quality, edge case consideration, and code documentation.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

🧪 SDET Interview Assignment

🎯Objective: ​
This assignment is designed to evaluate your ability to plan and execute a comprehensive testing strategy for a
web application. It will assess your analytical skills, understanding of testing principles, ability to write effective
test cases, and familiarity with automation tools.

🔗 Webpage Under Test


URL: Analytics Vidhya​
You will test this webpage as an external black-box tester. No access to source code or internal APIs will be
provided.

✅ Deliverables
Please organize all submissions into a single folder (or GitHub repo) with the following components:

1.📄 Test Strategy Document


Create a document outlining your test approach. It should include:​
- Overview: Your understanding of what the webpage does (based on visual inspection and behavior).​
- Scope of Testing: What is in-scope and out-of-scope.​
- Assumptions: Mention any assumptions made due to lack of backend access or documentation.​
- Types of Testing Covered:​
- Functional Testing​
- UI/UX Testing​
- Compatibility Testing (browsers/devices)​
- Responsive Design Testing​
- Negative Testing​
- Accessibility Testing​
- Performance Testing (basic strategy)​
- Security (basic surface-level checks)​
- Test Environments: List the browsers/devices/OS you plan to test on.​
- Tools You Would Use: Mention any tools you'd choose for manual or automated testing and justify your choice.

2.✅ Test Cases


Document at least 10-15 detailed test cases covering different aspects of the page. Include:​
- Test Case ID​
- Title​
- Description​
- Preconditions​
- Test Steps​
- Expected Result​
- Actual Result (if executed)​
- Priority/Severity​

Use a format like Excel, CSV, or Markdown.
3.🐞 Bug Report (Optional Bonus)
If you find any functional or visual bugs, include a short bug report for each:​
- Bug title​
- Steps to reproduce​
- Actual vs. expected behavior​
- Severity​
- Screenshot (if applicable)​

You may include this in the same test case document or separately.

4.🤖 Automation Samples (Mandatory)


You must include both frontend and backend automation test samples for the webpage using tools/frameworks
of your choice. Provide 2–3 sample test scripts for each.​

Frontend options (e.g.):​
- Selenium (Java/Python)​
- Playwright (JS/TS/Python)​
- Cypress (JavaScript)​

Backend options (e.g.):​
- REST Assured (Java)​
- Postman (with Newman CLI)​
- Python requests + pytest​

The above are some of the options. You are free to use the framework/language/library/tools that suits
you best.

Include:​
- A [Link] with setup instructions​
- Well-documented code with inline comments and function/method descriptions​
- Use of assertions and best practices (e.g., Page Object Model for frontend, structured API test suites for
backend)​

🔹

Code documentation is mandatory. Your code should be clean, modular, and easy to understand, with
appropriate comments and structure.

⏱️ Estimated Time & Submission Deadline


- Expected time commitment: 6–8 hours​
- Submit within 72 hours of receiving this assignment.

🧪 Evaluation Criteria
We’ll evaluate based on:​
- Thoughtfulness and clarity of the test strategy​
- Coverage and quality of test cases​

👨🏻‍💻💻
- Ability to think through edge cases and negative scenarios​
- Code documentation and readability
📩 Submission Instructions
- Package your files in a ZIP folder or upload them to a GitHub repository.​
- Email to: [varsha@[Link], sangeeta@[Link] ]​
- Subject: SDET Assignment - [Your Full Name]​
- If using GitHub, include the repo link in your email.

You might also like