Prioritize critical commercial user paths and assess failure impact across features.
Project-based Internship Programme
Build an Automated E-commerce QA Suite in a Software Testing Internship Project
This software testing online internship with certificate is a fee-based, project-based internship programme. This software testing online internship with certificate is a fee-based, project-based internship programme that focuses on modern quality assurance engineering. You design a risk-based test plan for an e-commerce platform, write comprehensive manual test cases, automate critical user journeys using Playwright and the Page Object Model, execute tests in GitHub Actions CI, and report defects using actionable traces and logs.
Decision note 01
Who this project fits and who it does not
A useful fit if…
- You want to master both foundational manual test design and modern automated browser testing with Playwright.
- You appreciate engineering discipline: designing robust Page Object Model architectures rather than fragile script recordings.
- You want to build a continuous integration testing pipeline that publishes clear HTML reports and failure traces on every pull request.
Choose another route if…
- You only want to click around websites randomly without writing structured test plans, boundary conditions, or automation code.
- You want to build full-stack web applications from scratch; our Full Stack Development programme focuses directly on feature development.
- You believe software testing is just about finding visual bugs rather than verifying data integrity, edge cases, and API responses.
Official assigned project
E
In modern software teams, quality assurance is an active engineering discipline, not an afterthought. In this Software Testing project, you act as the lead QA engineer for an e-commerce application. You analyze functional requirements, evaluate failure risks in purchase workflows, design systematic manual test cases, write automated browser tests using Playwright, and integrate your suite into GitHub Actions. You produce verifiable evidence that demonstrates software readiness and protects against regressions.
Task brief
E-commerce QA Automation Project - Create a practical QA suite combining test planning, manual cases, Playwright automation, and CI reporting.
Catalogue deliverables
- Risk-based test plan defining scope, critical paths, and test environment boundaries
- Comprehensive manual test case matrix with preconditions, boundary inputs, and expected outcomes
- Automated end-to-end Playwright test suite using the Page Object Model (POM) and auto-waiting
- GitHub Actions CI workflow executing test suites and publishing HTML artifacts and trace files
- Structured defect report documenting discovered bugs with reproduction steps, logs, and screenshots
How the project works
From requirement risk mapping to automated Playwright CI test pipelines
Quality engineering starts with risk-based test planning. Before writing a single line of automation code, you analyze the e-commerce application's core user journeys: product discovery, cart manipulation, discount code application, user authentication, and checkout. You classify risks by likelihood and business impact, prioritizing testing efforts where failures would directly prevent transactions.
Manual test case design establishes the baseline for automated coverage. You author formal test cases with explicit preconditions, parameterized inputs, and expected results. You apply boundary value analysis and equivalence partitioning to test edge cases - such as zero-quantity carts, out-of-stock items, invalid credit card formatting, and coupon expiration states - ensuring coverage extends far beyond basic happy paths.
Automation with Playwright brings speed, consistency, and resilience to regression testing. Instead of writing brittle scripts that rely on volatile XPath selectors, you employ the Page Object Model (POM) pattern and user-facing locators (such as roles, labels, and text). You leverage Playwright's built-in auto-waiting to eliminate flaky 'sleep' statements, ensuring tests wait intelligently for elements to become visible and actionable.
Continuous integration and defect reporting complete the QA lifecycle. You configure a GitHub Actions workflow that executes your Playwright suite across headless browsers on every commit. When a test fails, the pipeline automatically captures screenshots, video recordings, and interactive Playwright Trace files. You translate these failures into professional bug reports containing exact reproduction steps, expected versus actual outcomes, and network payloads.
Submission evidence
What makes this work reviewable
- Risk-based test strategy document detailing scope, priorities, and environment configurations.
- Manual test case spreadsheet/repository containing boundary values and positive/negative scenarios.
- Playwright test suite repository structured using the Page Object Model across multiple pages.
- GitHub Actions workflow YAML demonstrating automated test execution and artifact archiving.
- Sample Playwright HTML test report and trace viewer files capturing simulated failure states.
Your build path
Move from question to reviewable evidence
Analyze e-commerce application requirements to identify high-risk workflows such as checkout and cart updates. Analyze e-commerce user journeys, assess business risks, and define testing scope and environments.
Design structured manual test cases covering functional happy paths, boundary conditions, and invalid inputs. Author detailed manual test cases with boundary value inputs, expected states, and error validations.
Automate stable storefront journeys using Playwright, leveraging resilient locator strategies. Implement end-to-end tests in Playwright using the Page Object Model and resilient locator strategies.
Integrate the test suite into a continuous integration pipeline with automated HTML report generation. Configure GitHub Actions to execute test suites automatically in headless mode and generate HTML reports.
Log detailed defect tickets with console logs, network traces, and verified reproduction steps. Log reproducible defect reports with captured traces, verify bug fixes, and maintain the regression suite.
Private self-check
Is this project a reasonable learning fit?
Your answers remain in this browser tab and are not stored or sent.
Use these prompts for reflection; they are not an eligibility test.
Skills notebook
Build capability in a realistic order
These are general domain-learning suggestions, not confirmed HireeBridge tool requirements.
Test Strategy & Manual Design
Write unambiguous test cases with preconditions, test data, and expected states.
Formulate boundary tests for cart counts, string inputs, and payment validations.
Playwright Test Automation
Encapsulate UI page interactions into maintainable, reusable object classes.
Query elements using accessibility roles, labels, and data-testid attributes.
Authenticate users and seed test state programmatically before running UI journeys.
CI Execution & Defect Triage
Run headless browser tests on pull requests with parallel execution.
Inspect DOM snapshots, console logs, and network waterfalls from failed runs.
Document reproducible bug reports with severity ratings and environmental logs.
Review before submitting
Common Software Testing project mistakes
- 01
Using hardcoded pauses (sleep/timeout) to wait for elements
Rely on Playwright's built-in web-first assertions and auto-waiting rather than arbitrary timer delays that cause test flakiness.
- 02
Using fragile CSS or XPath selectors tied to visual styles
Target accessible user roles (such as getByRole('button', { name: 'Checkout' })) or test IDs rather than deep DOM paths.
- 03
Writing end-to-end tests without a Page Object Model structure
Separate test logic from UI selectors using Page Objects so UI changes require updates in only one file.
- 04
Automating tests before understanding manual test cases
Always outline the manual test steps and expected outcomes clearly before writing automation code.
- 05
Failing to capture failure artifacts in CI runs
Configure Playwright to save screenshots, video recordings, and traces on failure so remote CI issues can be investigated.
What reviewers check
Completeness against the assigned brief and deliverables; functional correctness; domain-relevant logic, data, metrics or implementation; required edge cases and failure handling; reproducible setup and submission evidence; and clear documentation of the completed work.
Reviewer
GreyRocks team
Catalogue validation notes
Run deterministic tests and verify setup, failure screenshots/traces, and report generation.
Evidence language
Draft an honest CV bullet
Keep placeholders until you can replace them with evidence from your own project.
- Engineered an automated end-to-end test suite in Playwright (TypeScript) covering [number] critical e-commerce purchase flows.
- Architected a Page Object Model framework, reducing test maintenance overhead by [percentage] across UI revisions.
- Integrated automated regression testing into GitHub Actions CI, executing [number] tests across Chromium, Firefox, and WebKit.
- Authored [number] manual test cases applying boundary value analysis and equivalence partitioning to payment workflows.
- Identified and logged [number] high-severity functional bugs with detailed reproduction steps, console logs, and trace artifacts.
Project readiness
Prepare a strong project submission
Certificate and verification
Completion comes before the credential
GreyRocks provides the official assessment and credential verification infrastructure for HireeBridge programmes. Enrolment and fee payment grant access to the project specification, e-commerce demo application, and review rubrics; they do not award a completion credential upon payment alone. To receive certification, you submit your test plan documentation, Playwright automation codebase, CI workflow logs, and defect reports. A QA assessor evaluates your locator stability, test structure, and reporting quality. Approved submissions earn an official certificate featuring a unique credential ID and QR code verifying authenticity on GreyRocks.
- Complete
- Submit
- Review
- Approval
- Credential ID and QR
Read the certificate process · Verify a credential on GreyRocks
Duration: 1 Month / 4 Weeks.
Plan inclusions: Each domain maps to an assigned project and task specification. Reference repositories and comprehensive materials depend on the selected plan; certificates follow task submission and explicit reviewer approval.
Questions from students
Software Testing internship FAQ
What specific application will I test during this internship?
You will test a functional demo e-commerce web application, covering vital user journeys including product catalog navigation, item search and filtering, cart management, user authentication, and checkout validation.
Why is Playwright chosen instead of Selenium for this project?
Playwright provides modern, fast, and reliable automation with native auto-waiting, multi-tab and multi-context support, built-in trace recording, and cross-browser testing across Chromium, Firefox, and WebKit without third-party driver installations.
Do I need prior coding experience to complete the automation portion?
Basic familiarity with JavaScript or TypeScript is helpful. The project guide provides step-by-step instruction on setting up Playwright, authoring locators, structuring Page Objects, and running tests.
What is the Page Object Model (POM) and why is it important?
The Page Object Model is an industry-standard architectural pattern that organizes web pages into reusable class objects. If a button label or input ID changes on the website, you only update it once in the Page Object file rather than across dozens of individual tests.
How do I prove that my automated tests ran in CI?
You include your GitHub Actions workflow configuration and provide links or screenshots of the workflow run history showing the green execution status and the attached Playwright HTML report artifact.
Can I complete both manual testing and automated testing in this project?
Yes. The project explicitly combines both: you first author a formal manual test plan and test case matrix, and then automate the high-priority, stable journeys using Playwright.
How long does the programme take to complete?
The programme is organized as a 4-week self-paced project, guiding you sequentially from test planning and manual design to Playwright scripting, CI pipeline integration, and defect reporting.
Is the certificate verifiable by employers?
Yes. Every certificate is recorded in the GreyRocks verification registry, containing a unique credential ID and QR code that employers can scan to verify your certified skills.
Next step
Choose your plan and start building.
Review plan details, included resources and the assigned project scope before you begin.