Ujjwal Kumar Singh
SDET
He/Him
I am Open to Speak, Write
Software Tester | Quality Adovcate | OSS Enthusiast | Visit https://beinghumantester.github.io/ to know more about me.

Achievements

Bio Builder
Career Champion
Avid Reader
Club Explorer
Article Maven
MoT Community Certificate
Scholarship Hero
MoT Streak
In the Loop
Collection Curator
Glossary Contributor
Meme Maker
Photo Historian
Author Debut
Introduction to accessibility testing
99 and Counting
STEC Superstar
Meme Machine
Inclusive Companion
Social Connector
Open to Opportunities
Found at 404
Picture Perfect

Certificates

MoT Community Certificate image
  • Ujjwal Kumar Singh's profile
Awarded for: Achieving 5 or more Community Star badges

Activity

<a href="https://www.ministryoftesting.com/satellites/mutation-testing-not-just-for-unit-tests" rel="noopener nofollow">Mutation testing - not just for unit tests</a> image
Mutation testing - not just for unit tests
Ujjwal Kumar Singh
Ujjwal Kumar Singh
is Open to Write
This badge is awarded to members who indicate they are open to work, writing, teaching, speaking, mentoring, CV reviewing or internships. image
This badge is awarded to members who indicate they are open to work, writing, teaching, speaking, mentoring, CV reviewing or internships.
Ujjwal Kumar Singh
Ujjwal Kumar Singh
is Open to Speak

Contributions

Dead Code image
  • Ujjwal Kumar Singh's profile
Dead code refers to parts of a codebase that exist but are never executed or have no effect on the program’s outcome. This includes unused functions, unreachable conditions, or variables that are never referenced. While dead code does not alter how an application runs, it adds unnecessary weight, creates confusion, and makes both development and testing harder to maintain.From a testing perspective, dead code often appears in coverage reports as lines that are never executed. Identifying it can be done through practices such as static analysis, where automated checks highlight unreachable or unused code, or through code coverage, where unexecuted paths stand out during test runs. Development environments may also issue warnings about unused variables or unreachable logic. In addition, runtime monitoring and peer reviews are effective ways to confirm whether suspicious blocks of code are ever exercised.Removing dead code improves clarity, reduces the effort of writing and maintaining tests, and ensures test results focus only on the active and meaningful parts of the system.
Login or sign up to create your own MoT page.
Subscribe to our newsletter
We'll keep you up to date on all the testing trends.