Skip to contentSkip to content
Verified credentials. On-chain. Forever.Learn more
Ewance
Sign in
Cover image for Kill Surviving Mutants in a Travel Pricing Service
Code

Kill Surviving Mutants in a Travel Pricing Service

FreeVerified credential2 weeksAdvanced

Overview

What this challenge is about.

Kill Surviving Mutants in a Travel Pricing Service. Advanced challenge in code. Writing production code that solves real engineering problems, earn a blockch...

CredentialBlockchain-anchored
ShareableLinkedIn-ready
LanguageEnglish
PaceSelf-paced

The Brief

What you'll do, and what you'll demonstrate.

Find where 91 percent line coverage hides ineffective tests and close that gap on the five highest-stakes pricing classes by killing surviving mutants.

This is not a coding exercise. It is the work a software engineer does between a Jira ticket and a merged PR. That distinction matters to every hiring manager who has seen candidates solve LeetCode problems and none who have shipped production code under real constraints.

When you finish, you will have something most graduates do not: a real-world deliverable, verified by Ewance, that you can show to a hiring manager and say "I did this. Here is the proof."

Earning criteria — what you'll demonstrate

  • Explain why line coverage overstates test effectiveness and how mutation testing measures what coverage cannot
  • Configure and run PIT against a Java service and interpret per-class mutation scores
  • Prioritize testing effort by business risk rather than by easiest wins
  • Write targeted JUnit 5 assertions that kill specific surviving mutants while keeping tests readable
  • Reason about the operational trade-offs of enforcing a mutation-score gate in continuous integration

Program Fit

Where this fits in your program.

Sharpens the same skills your degree expects you to demonstrate.

Aligned coursework coming soon.

Careers

Career paths this challenge builds toward

Completing this challenge demonstrates skills that transfer directly to these roles:

Software Engineer in Test

This challenge builds the core habit of judging tests by what they catch, not what they run. You leave able to measure test effectiveness, target the riskiest code, and defend testing investment with hard numbers — the daily work of an engineer who owns quality.

This challenge sharpens

  • mutation-testing
  • junit
  • test-strategy

Backend Java Engineer

Pricing logic is exactly the high-stakes backend code where silent bugs cost money. Practicing PIT on a Java service teaches you to ship business-critical code with tests that genuinely protect it, a skill backend teams value highly.

This challenge sharpens

  • java
  • mutation-testing
  • code-coverage

Build and Release Engineer

Deciding whether to gate builds on a mutation-score threshold is a real release-engineering trade-off between safety and speed. You finish able to weigh quality gates against build-time cost and recommend pipeline policy with evidence.

This challenge sharpens

  • ci-cd
  • mutation-testing
  • test-strategy

One more thing

You can put a credential on your CV by Friday.