Debugging Vocabulary: Verbs & Phrases Reference
Build your vocabulary of debugging verbs, idiomatic phrases, and technical expressions used when investigating and describing bugs in English.
0 / 50 completed
1 / 50
What does 'to bisect' mean in a Git debugging context?
'git bisect' uses binary search to find the commit that introduced a regression. You mark commits as 'good' or 'bad' and Git narrows down the range until it finds the culprit commit.
2 / 50
Which sentence correctly uses 'to reproduce' in a debugging context?
'To reproduce' (or 'to repro') means to make the bug happen again reliably using specific steps. 'I was able to reproduce the bug by...' is the standard formulation.
3 / 50
What does 'to narrow down' mean in debugging?
'Narrow down' means to progressively eliminate suspects until you've isolated the cause. 'I've narrowed it down to the authentication middleware' means everything else has been ruled out.
4 / 50
What does the phrase 'it works on my machine' typically imply?
'It works on my machine' is a classic engineering phrase implying environment inconsistency — the code behaves differently in development vs. staging or production due to different OS, env vars, dependencies, or data.
5 / 50
What does 'flaky test' mean?
A flaky test fails non-deterministically — sometimes it passes, sometimes it fails with no code change. Common causes: race conditions, time-dependent assertions, reliance on external APIs, or shared state between tests.
6 / 50
What does 'to instrument the code' mean?
Instrumenting code means adding observability: log statements, performance counters, traces, or metrics. 'We'll need to instrument the payment flow before we can diagnose the latency issue.'
7 / 50
Which phrase means 'to check whether a variable has the expected value at a specific point in execution'?
'To inspect' a variable means to examine its current value — in a debugger, via a print/log statement, or in a REPL. 'Let me inspect the response object to see what the API is actually returning.'
8 / 50
What does 'off-by-one error' mean?
An off-by-one (OBOE) error is a very common bug where a boundary is wrong by exactly 1 — iterating one too many or too few times, or accessing the wrong array index. Classic example: `for i in range(1, n)` when you meant `range(0, n)`.
9 / 50
What does 'to trace through' the code mean?
'Tracing through' code means following the execution path step by step — in your head, on paper, or with a debugger — to understand what actually happens at runtime. 'Let me trace through this function with the failing input.'
10 / 50
What does 'regression' mean in software testing?
A regression is when working functionality breaks after a change — code that used to work stops working. 'This commit introduced a regression in the payment flow' means the payment flow worked before this commit but not after.
11 / 50
Sarah: "Hey team, I've just submitted a PR with a new feature. It seems like the API call isn't returning the correct data format. Can someone take a look?"
Mark (after reviewing): "I'm seeing that the response is indeed malformed. I'm going to investigate the serialization logic."The question presents a realistic scenario where someone has identified a problem and is requesting assistance. 'Debug' accurately describes the process of systematically finding and fixing errors in code, which aligns with Mark's stated intention to investigate the serialization logic. Options A and B are close but miss the core action being requested; option D is entirely inappropriate for this stage.
12 / 50
David: "I've just pushed a new branch with some changes to the user authentication flow. The tests are failing intermittently, and I can't seem to get them to pass consistently. It's really frustrating!" Maria: "Have you tried running the tests multiple times?"The correct phrasing is 'to isolate the cause of a problem by dividing it into smaller parts.' Maria is suggesting David uses a common debugging technique – running tests repeatedly. This aims to capture intermittent failures and helps him pinpoint the source of the inconsistency; simply repeating the test doesn't address *why* it's failing, only that it's happening. The other options represent incorrect approaches to this specific scenario.
13 / 50
PR Description
Subject: Fix: Incorrect data returned from API endpoint.
Body:
I've identified an issue where the API endpoint for retrieving user profiles is returning a JSON object with incorrect formatting. The 'name' field is consistently being represented as a string instead of a proper name object, leading to display errors in the frontend. I'm currently investigating the serialization process and suspect a recent change introduced a bug.
Which phrase best describes the action suggested by this PR description?The PR description focuses on identifying and fixing a specific problem – the incorrect JSON format. Option 2, 'to immediately revert the changes and open a new branch with the previous version,' is the most appropriate response as it aligns directly with debugging: to isolate and resolve a code issue by restoring a known-good state. The other options are less focused on the core debugging process; escalating without investigation isn't ideal, reverting blindly can be premature, and assigning to QA doesn't address the immediate problem of the incorrect format.
14 / 50
Liam: "Hey team, I'm running a new integration test for the payment service. It seems to be failing intermittently, but when I run it directly, it passes. I've tried restarting my machine and everything!" Chloe replies: "Have you considered adding more logging around the core payment processing logic? Perhaps we can pinpoint where the failure is occurring."The key here is understanding that 'it works on my machine' doesn't guarantee a reliable test environment. The phrase 'this is a common situation when debugging locally' highlights the misconception – that running a test locally always reflects its behavior in a potentially complex, distributed system. Chloe's suggestion to add logging directly addresses this by attempting to reproduce the intermittent failure and identify the root cause within the actual execution flow of the payment service. The other options present incorrect assumptions about the nature of intermittent failures or inappropriate debugging strategies.
15 / 50
During a code review discussion about a new microservice, Alex says: "I've been trying to debug this issue with the message queue integration. I'm constantly seeing intermittent failures – sometimes it works, sometimes it doesn't. It seems like the processing logic isn't handling edge cases properly." Which of the following phrases best captures Alex's frustration and the approach he should take?
Alex is describing a situation with intermittent failures, suggesting that the problem isn't immediately obvious. 'To isolate the problem by meticulously stepping through the code line by line' (option 2) aligns with this – it describes the act of tracing execution to understand how the system behaves in different states and pinpointing where errors occur. The other options represent a less targeted or appropriate initial approach: eliminating causes is too broad, monitoring output alone won't reveal the root cause, and simply reporting without investigating is unproductive. Debugging intermittent issues often requires focused observation and controlled testing.
16 / 50
Sarah: "Hey team, I've just submitted a PR with a new feature. It seems like the API call isn't returning the correct data format. Can someone take a look?"
Mark (after reviewing): "I'm seeing that the response is indeed malformed. I'm going to investigate the serialization logic."The question presents a realistic scenario where someone has identified a problem and is requesting assistance. 'Debug' accurately describes the process of systematically finding and fixing errors in code, which aligns with Mark's stated intention to investigate the serialization logic. Options A and B are close but miss the core action being requested; option D is entirely inappropriate for this stage.
17 / 50
David: "I've just pushed a new branch with some changes to the user authentication flow. The tests are failing intermittently, and I can't seem to get them to pass consistently. It's really frustrating!" Maria: "Have you tried running the tests multiple times?"The correct phrasing is 'to isolate the cause of a problem by dividing it into smaller parts.' Maria is suggesting David uses a common debugging technique – running tests repeatedly. This aims to capture intermittent failures and helps him pinpoint the source of the inconsistency; simply repeating the test doesn't address *why* it's failing, only that it's happening. The other options represent incorrect approaches to this specific scenario.
18 / 50
PR Description
Subject: Fix: Incorrect data returned from API endpoint.
Body:
I've identified an issue where the API endpoint for retrieving user profiles is returning a JSON object with incorrect formatting. The 'name' field is consistently being represented as a string instead of a proper name object, leading to display errors in the frontend. I'm currently investigating the serialization process and suspect a recent change introduced a bug.
Which phrase best describes the action suggested by this PR description?The PR description focuses on identifying and fixing a specific problem – the incorrect JSON format. Option 2, 'to immediately revert the changes and open a new branch with the previous version,' is the most appropriate response as it aligns directly with debugging: to isolate and resolve a code issue by restoring a known-good state. The other options are less focused on the core debugging process; escalating without investigation isn't ideal, reverting blindly can be premature, and assigning to QA doesn't address the immediate problem of the incorrect format.
19 / 50
Liam: "Hey team, I'm running a new integration test for the payment service. It seems to be failing intermittently, but when I run it directly, it passes. I've tried restarting my machine and everything!" Chloe replies: "Have you considered adding more logging around the core payment processing logic? Perhaps we can pinpoint where the failure is occurring."The key here is understanding that 'it works on my machine' doesn't guarantee a reliable test environment. The phrase 'this is a common situation when debugging locally' highlights the misconception – that running a test locally always reflects its behavior in a potentially complex, distributed system. Chloe's suggestion to add logging directly addresses this by attempting to reproduce the intermittent failure and identify the root cause within the actual execution flow of the payment service. The other options present incorrect assumptions about the nature of intermittent failures or inappropriate debugging strategies.
20 / 50
During a code review discussion about a new microservice, Alex says: "I've been trying to debug this issue with the message queue integration. I'm constantly seeing intermittent failures – sometimes it works, sometimes it doesn't. It seems like the processing logic isn't handling edge cases properly." Which of the following phrases best captures Alex's frustration and the approach he should take?
Alex is describing a situation with intermittent failures, suggesting that the problem isn't immediately obvious. 'To isolate the problem by meticulously stepping through the code line by line' (option 2) aligns with this – it describes the act of tracing execution to understand how the system behaves in different states and pinpointing where errors occur. The other options represent a less targeted or appropriate initial approach: eliminating causes is too broad, monitoring output alone won't reveal the root cause, and simply reporting without investigating is unproductive. Debugging intermittent issues often requires focused observation and controlled testing.
21 / 50
Sarah: "Hey team, I've just submitted a PR with a new feature. It seems like the API call isn't returning the correct data format. Can someone take a look?"
Mark (after reviewing): "I'm seeing that the response is indeed malformed. I'm going to investigate the serialization logic."The question presents a realistic scenario where someone has identified a problem and is requesting assistance. 'Debug' accurately describes the process of systematically finding and fixing errors in code, which aligns with Mark's stated intention to investigate the serialization logic. Options A and B are close but miss the core action being requested; option D is entirely inappropriate for this stage.
22 / 50
David: "I've just pushed a new branch with some changes to the user authentication flow. The tests are failing intermittently, and I can't seem to get them to pass consistently. It's really frustrating!" Maria: "Have you tried running the tests multiple times?"The correct phrasing is 'to isolate the cause of a problem by dividing it into smaller parts.' Maria is suggesting David uses a common debugging technique – running tests repeatedly. This aims to capture intermittent failures and helps him pinpoint the source of the inconsistency; simply repeating the test doesn't address *why* it's failing, only that it's happening. The other options represent incorrect approaches to this specific scenario.
23 / 50
PR Description
Subject: Fix: Incorrect data returned from API endpoint.
Body:
I've identified an issue where the API endpoint for retrieving user profiles is returning a JSON object with incorrect formatting. The 'name' field is consistently being represented as a string instead of a proper name object, leading to display errors in the frontend. I'm currently investigating the serialization process and suspect a recent change introduced a bug.
Which phrase best describes the action suggested by this PR description?The PR description focuses on identifying and fixing a specific problem – the incorrect JSON format. Option 2, 'to immediately revert the changes and open a new branch with the previous version,' is the most appropriate response as it aligns directly with debugging: to isolate and resolve a code issue by restoring a known-good state. The other options are less focused on the core debugging process; escalating without investigation isn't ideal, reverting blindly can be premature, and assigning to QA doesn't address the immediate problem of the incorrect format.
24 / 50
Liam: "Hey team, I'm running a new integration test for the payment service. It seems to be failing intermittently, but when I run it directly, it passes. I've tried restarting my machine and everything!" Chloe replies: "Have you considered adding more logging around the core payment processing logic? Perhaps we can pinpoint where the failure is occurring."The key here is understanding that 'it works on my machine' doesn't guarantee a reliable test environment. The phrase 'this is a common situation when debugging locally' highlights the misconception – that running a test locally always reflects its behavior in a potentially complex, distributed system. Chloe's suggestion to add logging directly addresses this by attempting to reproduce the intermittent failure and identify the root cause within the actual execution flow of the payment service. The other options present incorrect assumptions about the nature of intermittent failures or inappropriate debugging strategies.
25 / 50
During a code review discussion about a new microservice, Alex says: "I've been trying to debug this issue with the message queue integration. I'm constantly seeing intermittent failures – sometimes it works, sometimes it doesn't. It seems like the processing logic isn't handling edge cases properly." Which of the following phrases best captures Alex's frustration and the approach he should take?
Alex is describing a situation with intermittent failures, suggesting that the problem isn't immediately obvious. 'To isolate the problem by meticulously stepping through the code line by line' (option 2) aligns with this – it describes the act of tracing execution to understand how the system behaves in different states and pinpointing where errors occur. The other options represent a less targeted or appropriate initial approach: eliminating causes is too broad, monitoring output alone won't reveal the root cause, and simply reporting without investigating is unproductive. Debugging intermittent issues often requires focused observation and controlled testing.
26 / 50
Sarah: "Hey team, I've just submitted a PR with a new feature. It seems like the API call isn't returning the correct data format. Can someone take a look?"
Mark (after reviewing): "I'm seeing that the response is indeed malformed. I'm going to investigate the serialization logic."The question presents a realistic scenario where someone has identified a problem and is requesting assistance. 'Debug' accurately describes the process of systematically finding and fixing errors in code, which aligns with Mark's stated intention to investigate the serialization logic. Options A and B are close but miss the core action being requested; option D is entirely inappropriate for this stage.
27 / 50
David: "I've just pushed a new branch with some changes to the user authentication flow. The tests are failing intermittently, and I can't seem to get them to pass consistently. It's really frustrating!" Maria: "Have you tried running the tests multiple times?"The correct phrasing is 'to isolate the cause of a problem by dividing it into smaller parts.' Maria is suggesting David uses a common debugging technique – running tests repeatedly. This aims to capture intermittent failures and helps him pinpoint the source of the inconsistency; simply repeating the test doesn't address *why* it's failing, only that it's happening. The other options represent incorrect approaches to this specific scenario.
28 / 50
PR Description
Subject: Fix: Incorrect data returned from API endpoint.
Body:
I've identified an issue where the API endpoint for retrieving user profiles is returning a JSON object with incorrect formatting. The 'name' field is consistently being represented as a string instead of a proper name object, leading to display errors in the frontend. I'm currently investigating the serialization process and suspect a recent change introduced a bug.
Which phrase best describes the action suggested by this PR description?The PR description focuses on identifying and fixing a specific problem – the incorrect JSON format. Option 2, 'to immediately revert the changes and open a new branch with the previous version,' is the most appropriate response as it aligns directly with debugging: to isolate and resolve a code issue by restoring a known-good state. The other options are less focused on the core debugging process; escalating without investigation isn't ideal, reverting blindly can be premature, and assigning to QA doesn't address the immediate problem of the incorrect format.
29 / 50
Liam: "Hey team, I'm running a new integration test for the payment service. It seems to be failing intermittently, but when I run it directly, it passes. I've tried restarting my machine and everything!" Chloe replies: "Have you considered adding more logging around the core payment processing logic? Perhaps we can pinpoint where the failure is occurring."The key here is understanding that 'it works on my machine' doesn't guarantee a reliable test environment. The phrase 'this is a common situation when debugging locally' highlights the misconception – that running a test locally always reflects its behavior in a potentially complex, distributed system. Chloe's suggestion to add logging directly addresses this by attempting to reproduce the intermittent failure and identify the root cause within the actual execution flow of the payment service. The other options present incorrect assumptions about the nature of intermittent failures or inappropriate debugging strategies.
30 / 50
During a code review discussion about a new microservice, Alex says: "I've been trying to debug this issue with the message queue integration. I'm constantly seeing intermittent failures – sometimes it works, sometimes it doesn't. It seems like the processing logic isn't handling edge cases properly." Which of the following phrases best captures Alex's frustration and the approach he should take?
Alex is describing a situation with intermittent failures, suggesting that the problem isn't immediately obvious. 'To isolate the problem by meticulously stepping through the code line by line' (option 2) aligns with this – it describes the act of tracing execution to understand how the system behaves in different states and pinpointing where errors occur. The other options represent a less targeted or appropriate initial approach: eliminating causes is too broad, monitoring output alone won't reveal the root cause, and simply reporting without investigating is unproductive. Debugging intermittent issues often requires focused observation and controlled testing.
31 / 50
Sarah: "Hey team, I've just submitted a PR with a new feature. It seems like the API call isn't returning the correct data format. Can someone take a look?"
Mark (after reviewing): "I'm seeing that the response is indeed malformed. I'm going to investigate the serialization logic."The question presents a realistic scenario where someone has identified a problem and is requesting assistance. 'Debug' accurately describes the process of systematically finding and fixing errors in code, which aligns with Mark's stated intention to investigate the serialization logic. Options A and B are close but miss the core action being requested; option D is entirely inappropriate for this stage.
32 / 50
David: "I've just pushed a new branch with some changes to the user authentication flow. The tests are failing intermittently, and I can't seem to get them to pass consistently. It's really frustrating!" Maria: "Have you tried running the tests multiple times?"The correct phrasing is 'to isolate the cause of a problem by dividing it into smaller parts.' Maria is suggesting David uses a common debugging technique – running tests repeatedly. This aims to capture intermittent failures and helps him pinpoint the source of the inconsistency; simply repeating the test doesn't address *why* it's failing, only that it's happening. The other options represent incorrect approaches to this specific scenario.
33 / 50
PR Description
Subject: Fix: Incorrect data returned from API endpoint.
Body:
I've identified an issue where the API endpoint for retrieving user profiles is returning a JSON object with incorrect formatting. The 'name' field is consistently being represented as a string instead of a proper name object, leading to display errors in the frontend. I'm currently investigating the serialization process and suspect a recent change introduced a bug.
Which phrase best describes the action suggested by this PR description?The PR description focuses on identifying and fixing a specific problem – the incorrect JSON format. Option 2, 'to immediately revert the changes and open a new branch with the previous version,' is the most appropriate response as it aligns directly with debugging: to isolate and resolve a code issue by restoring a known-good state. The other options are less focused on the core debugging process; escalating without investigation isn't ideal, reverting blindly can be premature, and assigning to QA doesn't address the immediate problem of the incorrect format.
34 / 50
Liam: "Hey team, I'm running a new integration test for the payment service. It seems to be failing intermittently, but when I run it directly, it passes. I've tried restarting my machine and everything!" Chloe replies: "Have you considered adding more logging around the core payment processing logic? Perhaps we can pinpoint where the failure is occurring."The key here is understanding that 'it works on my machine' doesn't guarantee a reliable test environment. The phrase 'this is a common situation when debugging locally' highlights the misconception – that running a test locally always reflects its behavior in a potentially complex, distributed system. Chloe's suggestion to add logging directly addresses this by attempting to reproduce the intermittent failure and identify the root cause within the actual execution flow of the payment service. The other options present incorrect assumptions about the nature of intermittent failures or inappropriate debugging strategies.
35 / 50
During a code review discussion about a new microservice, Alex says: "I've been trying to debug this issue with the message queue integration. I'm constantly seeing intermittent failures – sometimes it works, sometimes it doesn't. It seems like the processing logic isn't handling edge cases properly." Which of the following phrases best captures Alex's frustration and the approach he should take?
Alex is describing a situation with intermittent failures, suggesting that the problem isn't immediately obvious. 'To isolate the problem by meticulously stepping through the code line by line' (option 2) aligns with this – it describes the act of tracing execution to understand how the system behaves in different states and pinpointing where errors occur. The other options represent a less targeted or appropriate initial approach: eliminating causes is too broad, monitoring output alone won't reveal the root cause, and simply reporting without investigating is unproductive. Debugging intermittent issues often requires focused observation and controlled testing.
36 / 50
Sarah: "Hey team, I've just submitted a PR with a new feature. It seems like the API call isn't returning the correct data format. Can someone take a look?"
Mark (after reviewing): "I'm seeing that the response is indeed malformed. I'm going to investigate the serialization logic."The question presents a realistic scenario where someone has identified a problem and is requesting assistance. 'Debug' accurately describes the process of systematically finding and fixing errors in code, which aligns with Mark's stated intention to investigate the serialization logic. Options A and B are close but miss the core action being requested; option D is entirely inappropriate for this stage.
37 / 50
David: "I've just pushed a new branch with some changes to the user authentication flow. The tests are failing intermittently, and I can't seem to get them to pass consistently. It's really frustrating!" Maria: "Have you tried running the tests multiple times?"The correct phrasing is 'to isolate the cause of a problem by dividing it into smaller parts.' Maria is suggesting David uses a common debugging technique – running tests repeatedly. This aims to capture intermittent failures and helps him pinpoint the source of the inconsistency; simply repeating the test doesn't address *why* it's failing, only that it's happening. The other options represent incorrect approaches to this specific scenario.
38 / 50
PR Description
Subject: Fix: Incorrect data returned from API endpoint.
Body:
I've identified an issue where the API endpoint for retrieving user profiles is returning a JSON object with incorrect formatting. The 'name' field is consistently being represented as a string instead of a proper name object, leading to display errors in the frontend. I'm currently investigating the serialization process and suspect a recent change introduced a bug.
Which phrase best describes the action suggested by this PR description?The PR description focuses on identifying and fixing a specific problem – the incorrect JSON format. Option 2, 'to immediately revert the changes and open a new branch with the previous version,' is the most appropriate response as it aligns directly with debugging: to isolate and resolve a code issue by restoring a known-good state. The other options are less focused on the core debugging process; escalating without investigation isn't ideal, reverting blindly can be premature, and assigning to QA doesn't address the immediate problem of the incorrect format.
39 / 50
Liam: "Hey team, I'm running a new integration test for the payment service. It seems to be failing intermittently, but when I run it directly, it passes. I've tried restarting my machine and everything!" Chloe replies: "Have you considered adding more logging around the core payment processing logic? Perhaps we can pinpoint where the failure is occurring."The key here is understanding that 'it works on my machine' doesn't guarantee a reliable test environment. The phrase 'this is a common situation when debugging locally' highlights the misconception – that running a test locally always reflects its behavior in a potentially complex, distributed system. Chloe's suggestion to add logging directly addresses this by attempting to reproduce the intermittent failure and identify the root cause within the actual execution flow of the payment service. The other options present incorrect assumptions about the nature of intermittent failures or inappropriate debugging strategies.
40 / 50
During a code review discussion about a new microservice, Alex says: "I've been trying to debug this issue with the message queue integration. I'm constantly seeing intermittent failures – sometimes it works, sometimes it doesn't. It seems like the processing logic isn't handling edge cases properly." Which of the following phrases best captures Alex's frustration and the approach he should take?
Alex is describing a situation with intermittent failures, suggesting that the problem isn't immediately obvious. 'To isolate the problem by meticulously stepping through the code line by line' (option 2) aligns with this – it describes the act of tracing execution to understand how the system behaves in different states and pinpointing where errors occur. The other options represent a less targeted or appropriate initial approach: eliminating causes is too broad, monitoring output alone won't reveal the root cause, and simply reporting without investigating is unproductive. Debugging intermittent issues often requires focused observation and controlled testing.
41 / 50
Sarah: "Hey team, I've just submitted a PR with a new feature. It seems like the API call isn't returning the correct data format. Can someone take a look?"
Mark (after reviewing): "I'm seeing that the response is indeed malformed. I'm going to investigate the serialization logic."The question presents a realistic scenario where someone has identified a problem and is requesting assistance. 'Debug' accurately describes the process of systematically finding and fixing errors in code, which aligns with Mark's stated intention to investigate the serialization logic. Options A and B are close but miss the core action being requested; option D is entirely inappropriate for this stage.
42 / 50
David: "I've just pushed a new branch with some changes to the user authentication flow. The tests are failing intermittently, and I can't seem to get them to pass consistently. It's really frustrating!" Maria: "Have you tried running the tests multiple times?"The correct phrasing is 'to isolate the cause of a problem by dividing it into smaller parts.' Maria is suggesting David uses a common debugging technique – running tests repeatedly. This aims to capture intermittent failures and helps him pinpoint the source of the inconsistency; simply repeating the test doesn't address *why* it's failing, only that it's happening. The other options represent incorrect approaches to this specific scenario.
43 / 50
PR Description
Subject: Fix: Incorrect data returned from API endpoint.
Body:
I've identified an issue where the API endpoint for retrieving user profiles is returning a JSON object with incorrect formatting. The 'name' field is consistently being represented as a string instead of a proper name object, leading to display errors in the frontend. I'm currently investigating the serialization process and suspect a recent change introduced a bug.
Which phrase best describes the action suggested by this PR description?The PR description focuses on identifying and fixing a specific problem – the incorrect JSON format. Option 2, 'to immediately revert the changes and open a new branch with the previous version,' is the most appropriate response as it aligns directly with debugging: to isolate and resolve a code issue by restoring a known-good state. The other options are less focused on the core debugging process; escalating without investigation isn't ideal, reverting blindly can be premature, and assigning to QA doesn't address the immediate problem of the incorrect format.
44 / 50
Liam: "Hey team, I'm running a new integration test for the payment service. It seems to be failing intermittently, but when I run it directly, it passes. I've tried restarting my machine and everything!" Chloe replies: "Have you considered adding more logging around the core payment processing logic? Perhaps we can pinpoint where the failure is occurring."The key here is understanding that 'it works on my machine' doesn't guarantee a reliable test environment. The phrase 'this is a common situation when debugging locally' highlights the misconception – that running a test locally always reflects its behavior in a potentially complex, distributed system. Chloe's suggestion to add logging directly addresses this by attempting to reproduce the intermittent failure and identify the root cause within the actual execution flow of the payment service. The other options present incorrect assumptions about the nature of intermittent failures or inappropriate debugging strategies.
45 / 50
During a code review discussion about a new microservice, Alex says: "I've been trying to debug this issue with the message queue integration. I'm constantly seeing intermittent failures – sometimes it works, sometimes it doesn't. It seems like the processing logic isn't handling edge cases properly." Which of the following phrases best captures Alex's frustration and the approach he should take?
Alex is describing a situation with intermittent failures, suggesting that the problem isn't immediately obvious. 'To isolate the problem by meticulously stepping through the code line by line' (option 2) aligns with this – it describes the act of tracing execution to understand how the system behaves in different states and pinpointing where errors occur. The other options represent a less targeted or appropriate initial approach: eliminating causes is too broad, monitoring output alone won't reveal the root cause, and simply reporting without investigating is unproductive. Debugging intermittent issues often requires focused observation and controlled testing.
46 / 50
Sarah: "Hey team, I've just submitted a PR with a new feature. It seems like the API call isn't returning the correct data format. Can someone take a look?"
Mark (after reviewing): "I'm seeing that the response is indeed malformed. I'm going to investigate the serialization logic."The question presents a realistic scenario where someone has identified a problem and is requesting assistance. 'Debug' accurately describes the process of systematically finding and fixing errors in code, which aligns with Mark's stated intention to investigate the serialization logic. Options A and B are close but miss the core action being requested; option D is entirely inappropriate for this stage.
47 / 50
David: "I've just pushed a new branch with some changes to the user authentication flow. The tests are failing intermittently, and I can't seem to get them to pass consistently. It's really frustrating!" Maria: "Have you tried running the tests multiple times?"The correct phrasing is 'to isolate the cause of a problem by dividing it into smaller parts.' Maria is suggesting David uses a common debugging technique – running tests repeatedly. This aims to capture intermittent failures and helps him pinpoint the source of the inconsistency; simply repeating the test doesn't address *why* it's failing, only that it's happening. The other options represent incorrect approaches to this specific scenario.
48 / 50
PR Description
Subject: Fix: Incorrect data returned from API endpoint.
Body:
I've identified an issue where the API endpoint for retrieving user profiles is returning a JSON object with incorrect formatting. The 'name' field is consistently being represented as a string instead of a proper name object, leading to display errors in the frontend. I'm currently investigating the serialization process and suspect a recent change introduced a bug.
Which phrase best describes the action suggested by this PR description?The PR description focuses on identifying and fixing a specific problem – the incorrect JSON format. Option 2, 'to immediately revert the changes and open a new branch with the previous version,' is the most appropriate response as it aligns directly with debugging: to isolate and resolve a code issue by restoring a known-good state. The other options are less focused on the core debugging process; escalating without investigation isn't ideal, reverting blindly can be premature, and assigning to QA doesn't address the immediate problem of the incorrect format.
49 / 50
Liam: "Hey team, I'm running a new integration test for the payment service. It seems to be failing intermittently, but when I run it directly, it passes. I've tried restarting my machine and everything!" Chloe replies: "Have you considered adding more logging around the core payment processing logic? Perhaps we can pinpoint where the failure is occurring."The key here is understanding that 'it works on my machine' doesn't guarantee a reliable test environment. The phrase 'this is a common situation when debugging locally' highlights the misconception – that running a test locally always reflects its behavior in a potentially complex, distributed system. Chloe's suggestion to add logging directly addresses this by attempting to reproduce the intermittent failure and identify the root cause within the actual execution flow of the payment service. The other options present incorrect assumptions about the nature of intermittent failures or inappropriate debugging strategies.
50 / 50
During a code review discussion about a new microservice, Alex says: "I've been trying to debug this issue with the message queue integration. I'm constantly seeing intermittent failures – sometimes it works, sometimes it doesn't. It seems like the processing logic isn't handling edge cases properly." Which of the following phrases best captures Alex's frustration and the approach he should take?
Alex is describing a situation with intermittent failures, suggesting that the problem isn't immediately obvious. 'To isolate the problem by meticulously stepping through the code line by line' (option 2) aligns with this – it describes the act of tracing execution to understand how the system behaves in different states and pinpointing where errors occur. The other options represent a less targeted or appropriate initial approach: eliminating causes is too broad, monitoring output alone won't reveal the root cause, and simply reporting without investigating is unproductive. Debugging intermittent issues often requires focused observation and controlled testing.
Frequently Asked Questions
What does the "Debugging Vocabulary: Verbs & Phrases Reference" exercise practise?
Build your vocabulary of debugging verbs, idiomatic phrases, and technical expressions used when investigating and describing bugs in English.
How many questions are in this exercise?
This exercise has 50 questions, each multiple-choice with a full explanation shown after you answer.
What English level is this exercise for?
This exercise is tagged Intermediate. If the vocabulary feels difficult, browse the Debugging Language category page for an easier module to start with.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free with no account, sign-up, or paywall.
Do I get feedback if I answer incorrectly?
Yes — whichever option you choose, right or wrong, you'll immediately see an explanation clarifying the correct term and why the other options don't fit.
Can I retry this exercise?
Yes — once you finish all the questions, a "Try again" button on the results screen resets the exercise so you can practise as many times as you like.
Do I need an account to track my progress?
No account is required. Your progress bar and score for this session are tracked in the browser as you go, but nothing is saved once you leave the page.
Is "Debugging Vocabulary: Verbs & Phrases Reference" part of a larger series?
Yes — it's one exercise in the Debugging Language category on CoderSlingo. See the category page for the full list of related exercises on similar terminology.
Can I link directly to this exercise?
Yes — this exercise has its own permanent URL, so you can bookmark it or share the link directly with a colleague or study partner.
Where can I find more exercises like this one?
See the Debugging Language category page for related exercises, or browse the main Exercises hub for other IT English topics.