Critical Bug
A critical bug is a severe software defect that prevents core functionality from working, causes data loss or corruption, creates security vulnerabilities, or makes the application essentially unusable for its intended purpose.
Understanding Critical Bug
Critical bugs are the most serious category of software defects. They include issues like checkout flows that fail silently, authentication systems that can be bypassed, data that gets corrupted on save, and crashes that occur during normal usage. A critical bug typically means the application should not be released or, if already live, needs an immediate fix.
Vibecoded applications are particularly prone to critical bugs in areas that involve complex logic or sensitive operations. AI-generated payment processing code might not properly validate amounts. Authentication code might have exploitable gaps. Data handling code might lose or corrupt information under specific conditions. These are exactly the kinds of issues that a vibecoder might not think to test because they did not write the code and may not understand the potential failure modes.
DidItWork classifies bugs by severity, ensuring that critical issues are flagged with the highest priority. When a tester finds a bug that prevents core functionality from working or puts user data at risk, it is reported as critical, giving the developer clear guidance on what to fix first.
Example usage
“A critical bug in the payment flow was charging customers twice. It only happened when the user clicked the pay button during a slow network connection.”
Related terms
Learn more
Bug
A bug is a flaw, error, or defect in a software application that causes it to produce incorrect results, behave unexpectedly, or fail to perform its intended function.
Read moreSecurity Vulnerability
A security vulnerability is a weakness or flaw in a software application that could be exploited by an attacker to gain unauthorized access, steal data, disrupt service, or perform other malicious actions.
Read moreBug Report
A bug report is a formal document that describes a software defect, including the steps to reproduce it, the expected behavior, the actual behavior observed, and relevant context such as device, browser, and screenshots.
Read more