Write the rule the test protects
Use an application you own. For this original project, a booking service has one available place. A request supplies a booking identifier; sending the same identifier and unchanged details again must return the existing booking, not create another. Reusing that identifier with different details is a conflict. These are the project’s chosen rules, not behavior every API automatically provides.
The central check is simple: confirmed bookings must never exceed capacity. A message saying “success” is not enough; inspect the stored outcome too. That makes the test useful even when a broken service returns a plausible response.
Test the repeated and overlapping requests
Start each independent scenario from its stated state. The concurrency case is not just the last row of a sequential script.
| Scenario | Expected result under this contract |
|---|---|
| Empty service; submit booking K1 | One booking is created |
| K1 already exists; repeat the same details | Return K1; still one booking |
| K1 exists; send different details with K1 | Report a conflict; preserve the stored booking |
| K1 exists; submit a different booking K2 | Reject because capacity is full |
| Empty service; K1 and K2 arrive concurrently | At most one booking is confirmed |
- A broken sequence can let both requests read “one place available” before either saves. Each check passes individually, yet both bookings are created.
- The capacity check and reservation must work as one protected operation under the chosen storage system. Test the final count after deliberately overlapping the requests; a sequential happy-path test will miss this defect.
- Reproduce the failure locally, repair it and rerun the same test. Keep the failing version or patch so a reviewer can see what the test caught.
Make the report useful to the person fixing the bug
Write the starting state, exact request sequence, expected result, observed result and stored count. A concise report such as “Two concurrent requests create two confirmed bookings when capacity is one” communicates more than “Booking test failed.” Include the smallest reproduction that still fails.
Separate fast rule checks from the smaller tests that involve storage and concurrency. Avoid treating a sleep as proof that a background action has finished. Use a defined completion condition and investigate unstable failures rather than rerunning them until they pass.
After doing the project, describe the booking rule and defect in your résumé. Do not claim complete coverage merely because all current tests pass. In an interview, explain a behavior you chose not to automate and why. Ask whether interns design tests and investigate failures, or primarily execute an existing test plan.
Before you apply
- Eligibility
- Check whether the role requires writing test software, investigating defects or executing a defined checklist. Prepare for the actual assignment.
- Timing
- Search the employer’s student route for the intended term; dedicated quality roles need not appear every cycle.
- Location
- Ask whether the tests need physical products or laboratory access. Software and instrument testing may use different setups.
- Pay
- Compare the offer’s actual rate and hours. Confirm which test devices and tools are supplied.
Job titles to search
- SDET or software engineer in test intern
- Build maintainable test software and infrastructure.
- Software quality engineering intern
- Choose tests by product risk and investigate failures.
- Test automation intern
- Make repeated checks reliable and their failures understandable.
Where to look
Search routes, not confirmed vacancies.
Datadog early careers
Inspect technical internship postings for test infrastructure or software-quality responsibilities.
Search: test · quality · software engineering intern
Keysight students and graduates
Its student route includes software, engineering and quality. Check which product and type of test the role concerns.
Search: software quality · test automation · software intern
Compare the work and try an example
Use a role comparison or worked exercise to choose your preparation before tailoring an application.
Sources
Employer information applies to the linked program. Our practice cases are not employer assessments.
- Datadog early careers
Internship and co-op lengths, typical recruiting cadence, role families, and workplace expectations. Confirm the specific office and term on each listing.
Checked - Keysight students and graduates
Student program eligibility, minimum placement length, and engineering and business functions. Reviewed in a rendered browser; individual roles may impose narrower requirements.
Checked
About this guide
Published by InternshipDeadlines. Guide reviewed . How we use sources.
Cite this guide
InternshipDeadlines. Software quality internships: SDET roles and a test project. Reviewed . https://internshipdeadlines.com/industries/software-quality-engineering/
Use the dates attached to the sources behind your claim. An editorial update does not reverify every source or confirm that an internship is open.