Interview Insights · Software Tester
How I Spot a Copy-Pasted Software Tester Project in Minutes
Quick summary — Copy-pasted test project
A copied project is not exposed by its content. It is exposed when the candidate cannot explain a single decision inside it. Many tester portfolios use the same public demo apps, the same tutorial frameworks and the same generic test cases. Using a demo app is fine. The problem is when nothing in the project reflects your own work: no real bugs found, no adapted test data, no reasons for the structure. Interviewers check this with a few follow-up questions. The fix is to add your own defects, decisions and changes so that every part of the project has a story.
In this guide you will learn:
- The four signals that make a testing project look copied
- What tutorial automation code gives away in a repository
- Why real bug reports are the strongest proof of ownership
- The follow-up questions interviewers use to probe a project
- A rework checklist to turn a borrowed project into your own
SECTION 01Signals in the test documents of a copied project
The first place I look is the test case sheet or the project section of the resume. Copied projects have a recognisable texture. The test cases are written for the famous demo flows, login and add to cart, with steps so generic they could apply to any website. There are no module-specific rules, no business conditions and no test data that hints at a real domain.
An owned project usually has small, odd details. A test case about what happens when a leave request crosses a weekend. A note that the date picker failed on one browser. A test data column with a user who has no manager assigned. Those details come from someone actually exploring the app.
| Document part | Copied version | Owned version | What I conclude |
|---|---|---|---|
| Test case title | Verify login with valid credentials | Verify leave request over a weekend counts 2 working days | Owned case shows domain thinking |
| Test data | username: admin, password: admin123 | Employee with no manager, employee on probation | Owned data reflects real roles |
| Expected result | User should be able to login | Balance drops by 2, manager gets one notification | Owned result is checkable |
| Coverage note | All modules tested | Payroll not tested, no access to that role | Honest scope signals ownership |
TC_01 Verify login with valid credentials
Pre-condition: User is on login page
Steps:
1. Enter valid username
2. Enter valid password
3. Click login
Expected: User should be logged in successfully
Status: Pass
(Could belong to any project on the internet.)TC_LV_07 Leave request spanning a weekend
Module: Leave > Apply
Pre-condition: Employee E103 has 10 casual leaves,
weekly off Saturday and Sunday
Test data: From Fri 14th to Mon 17th
Steps:
1. Log in as E103
2. Apply casual leave 14th to 17th
3. Submit and check leave summary
Expected:
- Leave counted as 2 days (Fri, Mon), not 4
- Balance shows 8
- Manager M20 receives one approval request
Actual: Counted as 4 days -> BUG-LV-03 raised
The owned test case also led to a bug. That link between a specific case and a real defect is the strongest sign that a person, not a template, did the testing.
SECTION 02What tutorial automation code gives away
If the resume mentions a Selenium framework, I open the repository or ask the candidate to describe it. Copied frameworks have clear signs: class names straight from a video course, a BaseTest with configuration for browsers that are never used, utility classes nobody calls, and Thread.sleep scattered everywhere because the original author used it as a quick fix.
None of this is a crime. Everyone learns from tutorials. What matters is whether the candidate has changed anything, and whether they can explain why the code is structured the way it is. A framework that has been adapted, even slightly, always has a story behind it.
| Code signal | What it suggests | Question I ask | Owned answer sounds like |
|---|---|---|---|
| Thread.sleep(5000) in many places | Copied quick fixes | Why sleep here and not a wait? | I replaced them with explicit waits after flaky runs |
| Unused utility classes | Framework pasted whole | What does ExcelUtil do in your tests? | I removed it, I use JSON test data |
| Absolute XPath locators | Recorded or copied locators | What happens if a div is added? | I switched to IDs and data-test attributes |
| Commit history of one big upload | No iterative work | What did you change in week two? | Added retry for a flaky upload test |
// Typical pasted test method
@Test
public void loginTest() throws InterruptedException {
driver.findElement(By.xpath("/html/body/div[1]/div/div[2]/form/input[1]"))
.sendKeys("admin");
driver.findElement(By.xpath("/html/body/div[1]/div/div[2]/form/input[2]"))
.sendKeys("admin123");
driver.findElement(By.xpath("/html/body/div[1]/div/div[2]/form/button"))
.click();
Thread.sleep(5000);
System.out.println("Login done");
}
// No assertion. Fragile locators. Fixed sleep.// Same test after the candidate reworked it
@Test
public void employeeCanApplyWeekendSpanningLeave() {
LoginPage login = new LoginPage(driver);
LeavePage leave = login.loginAs(users.get("E103"));
leave.apply("Casual", "2026-11-13", "2026-11-16");
WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(10));
wait.until(ExpectedConditions.visibilityOfElementLocated(
By.cssSelector("[data-test='leave-summary']")));
Assert.assertEquals(leave.daysCounted(), 2,
"Weekend days must not be counted");
}
The owned version has a test name that describes a business rule, an explicit wait instead of a fixed sleep, a stable CSS selector and a real assertion. Each change is a decision the candidate can talk about for a minute.
SECTION 03The follow-up questions that expose a borrowed project
I rarely need more than three or four questions. I am not trying to trap anyone. I am looking for one moment where the candidate talks about the project as something they lived through: a bug that surprised them, a test that kept failing, a decision they changed their mind about.
Candidates with copied projects answer every question at the level of the README. Candidates with owned projects drift into specifics without being asked, because they remember the frustrating parts. Prepare for these questions honestly and you will not need to fear them.
| Follow-up question | Copied answer | Owned answer | Signal |
|---|---|---|---|
| What was the hardest bug to reproduce? | All bugs were easy | Date picker failed only after timezone change | Real exploration |
| Which test was flaky and why? | No test was flaky | Upload test failed when the toast covered the button | Real execution |
| What would you test next with more time? | Everything is covered | Payroll role and mobile view | Honest scope |
| What did you change from the original design? | Nothing, it works | Moved test data out of code into JSON | Real decisions |
BUG-LV-03
Title: Leave spanning weekend counts Sat and Sun as leave days
Module: Leave > Apply
Build/Env: demo build of Nov, Chrome 130, Windows 11
Severity: Major Priority: High
Steps:
1. Log in as employee E103 (10 CL balance)
2. Apply CL from Fri 14th to Mon 17th
3. Open Leave Summary
Expected: 2 days counted, balance 8
Actual: 4 days counted, balance 6
Notes: Same issue for Earned Leave.
Holiday on 14th also counted. Screenshot attached."In my leave management project, the bug I am proudest
of is a weekend counting issue. I noticed the balance
dropped by 4 for a Friday to Monday leave. I checked
whether it was only casual leave, it was not, so I raised
it as Major with High priority because it directly
affects salary deductions. After that I added three
more cases around holidays and weekends, and one of
them found that public holidays were also counted."
Notice how the spoken story naturally answers the follow-ups before they are asked: what the bug was, how it was isolated, why it got that severity and what testing it led to next.
SECTION 04Rework checklist: make a borrowed project your own
If your project started from a tutorial, you do not need to throw it away. You need to add your own layer on top of it. Work through these sheets over a couple of weekends and every part of the project will have a story.
MAKE IT YOURS
[ ] Pick one module tutorials ignore and test it deeply
[ ] Write at least 15 test cases with real business rules
[ ] Log at least 3 real bugs with build, env, steps, evidence
[ ] Replace every Thread.sleep with an explicit wait
[ ] Replace absolute XPaths with IDs or CSS selectors
[ ] Add assertions to every automated test
[ ] Move test data out of code (JSON, CSV or properties)
[ ] Delete classes and configs you do not use
[ ] Commit changes in small steps with clear messages
[ ] Write a README section: what I changed and whyPREPARE ONE ANSWER FOR EACH
My best bug:
What, how I found it, severity and why ________
My flakiest test:
Symptom, cause, fix ___________________________
One design change:
Before, after, reason _________________________
What is not covered:
Modules or devices I skipped and why ___________
What I would add next:
API tests in Postman? Mobile view? ____________## What I built on top of the starter framework
- Tested the Leave module in depth (22 test cases)
- Found 4 defects, see /bugs for full reports
- Replaced fixed sleeps with WebDriverWait
- Switched locators to data-test attributes
- Test users stored in testdata/users.json
- Added a TestNG listener that saves a screenshot on failure
## Not covered yet
- Payroll module (no test account for that role)
- Mobile layout
(Use your own real numbers here.)
SECTION 05Ways to present a testing project as truly yours
How you talk about the project matters as much as what is inside it.
- Start with a bug, not a tool — Open your project story with the most interesting defect you found. It proves exploration faster than any list of tools.
- Say what you changed — Be open that you started from a tutorial framework, then explain what you added or fixed. Honesty plus change is convincing.
- Name what you did not cover — Stating the gaps in your coverage shows real understanding of your own project and of testing limits.
- Keep evidence ready — Have the repository, the test case sheet and two bug reports ready to share on screen during an online interview.
- Use your own numbers carefully — Mention only counts you can back up, such as the number of test cases you wrote. Inflated numbers fall apart under follow-up questions.
SECTION 06Interview Q&A — Copy-pasted test project
Q1Walk me through the testing project on your resume.
I tested the leave module of an HR demo app. I started from the requirements I could infer, wrote around 20 test cases on leave rules, and found a defect where weekends were counted as leave days. I automated the stable cases in Selenium with Java and TestNG, using page objects and explicit waits. Payroll was not covered because I had no access to that role.
Q2Did you build this Selenium framework yourself?
I started from a tutorial structure and then changed it for my tests. I removed utilities I did not use, replaced fixed sleeps with explicit waits after flaky runs, switched to CSS selectors with data-test attributes, and moved test data into a JSON file. I can explain each of those changes.
Q3What was the most interesting bug you found in your project?
A leave from Friday to Monday reduced the balance by four days instead of two. I checked other leave types and found the same issue, then tested holidays and found public holidays were also counted. I logged it as Major severity, High priority, because it would affect salary deductions.
Q4Why are there no assertions in some of your automated tests?
Those were from the starting code and I should have fixed them. A test without an assertion only proves the script ran. I have since added assertions on the actual result, such as the number of leave days counted, so a test fails when the behaviour is wrong.
Q5How would you extend this project with more time?
I would add API tests in Postman for the leave endpoints, checking status codes and leave balance values, because they run faster than UI tests. I would also test the mobile layout and add a simple CI run so the suite runs on every commit.
SECTION 07Test yourself — Copy-pasted test project quiz
Five questions. No sign-up.
0 / 5Pick an answer to see why it is right or wrong.
SECTION 08Frequently asked questions
How do interviewers know if a software testing project is copied?
They ask follow-up questions about bugs you found, flaky tests, design choices and gaps in coverage. Copied projects only have README-level answers. Owned projects come with specific details and stories.
Is it okay to use a demo website for a manual testing project?
Yes. Most freshers use demo apps. Make it yours by testing a module that tutorials skip, writing business-rule test cases and logging real bugs with full details.
Can I use a Selenium framework from a YouTube tutorial in my resume project?
You can start from one, but rework it. Replace fixed sleeps with waits, fix locators, add assertions, move test data out of code and be ready to explain every change you made.
What should a software tester fresher project include?
A short test plan, test cases with real rules and data, at least a few genuine bug reports, and optionally automation or API tests. Also include a note on what you did not cover and why.
How many bugs should my testing project show?
There is no fixed number. A few well-documented, real bugs with clear steps and evidence are far better than many vague ones. Make sure you can explain each bug you list.
Does Uncodemy help with Software Tester interview answers?
Yes. Uncodemy's Software Testing Training Course in Noida (classroom and online) includes live projects, one-to-one mock interviews and resume reviews, so you practise Software Tester interview answers with trainer feedback before the real interview. You can book a free demo class from this page to see how the sessions work.
SECTION 09Related reads
Classroom & online · Noida
Build a testing project you can defend
Our Software Testing Training Course gives you live projects with real modules to test, guided bug reporting and a Selenium framework you build step by step, so every part has your story.
Talk to a counsellor for current fees- Live project testing
- Framework built from scratch
- Bug report reviews
- Project-based mock interviews