<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Priyanka</title>
    <description>The latest articles on DEV Community by Priyanka (@priyanka_desai).</description>
    <link>https://dev.to/priyanka_desai</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4250628%2F0869bb7e-cdc6-4604-80de-7decb95ba16f.jpeg</url>
      <title>DEV Community: Priyanka</title>
      <link>https://dev.to/priyanka_desai</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/priyanka_desai"/>
    <language>en</language>
    <item>
      <title>UI vs Functional vs Network Bugs: How to Tell Them Apart</title>
      <dc:creator>Priyanka</dc:creator>
      <pubDate>Wed, 18 Nov 2026 22:08:04 +0000</pubDate>
      <link>https://dev.to/priyanka_desai/ui-vs-functional-vs-network-bugs-how-to-tell-them-apart-2dga</link>
      <guid>https://dev.to/priyanka_desai/ui-vs-functional-vs-network-bugs-how-to-tell-them-apart-2dga</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://bughuntlab.hashnode.dev/ui-vs-functional-vs-network-bugs-how-to-tell-them-apart" rel="noopener noreferrer"&gt;bughuntlab.hashnode.dev&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Four defect classes, one triage question, and why misclassifying costs you more than missing the bug.&lt;/p&gt;

&lt;p&gt;The most common mistake in junior defect reports is not a missing screenshot. It is &lt;strong&gt;misclassification&lt;/strong&gt; — calling something a UI bug when it is a network bug, or a functional bug when it is a validation bug.&lt;/p&gt;

&lt;p&gt;This matters more than it sounds. Classification decides &lt;em&gt;who fixes it&lt;/em&gt;, and a ticket that starts in the wrong queue loses a day before it even gets assigned.&lt;/p&gt;

&lt;h2&gt;
  
  
  The one question that separates them
&lt;/h2&gt;

&lt;p&gt;For any observed wrong behaviour, ask: &lt;strong&gt;where did the wrong thing first happen?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Not where you noticed it. Where it &lt;em&gt;originated&lt;/em&gt;.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;If the wrong thing happened...&lt;/th&gt;
&lt;th&gt;Class&lt;/th&gt;
&lt;th&gt;Who fixes it&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;In the pixels only&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;UI&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Front-end / design&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;In the app's logic&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Functional&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Front-end or back-end&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;In the request or response&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Network&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Back-end / API&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;In what input was accepted&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Validation&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Either, but usually API&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  UI defects
&lt;/h2&gt;

&lt;p&gt;The behaviour is correct. The &lt;strong&gt;rendering&lt;/strong&gt; is wrong.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Prices showing &lt;code&gt;£12.500&lt;/code&gt; instead of &lt;code&gt;£12.50&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;A disabled button that still looks enabled&lt;/li&gt;
&lt;li&gt;Text overflowing its container on a 320px viewport&lt;/li&gt;
&lt;li&gt;A toast appearing behind a modal&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The tell: if you read the underlying data (from the DOM, or a response), it is right. Only the presentation is wrong.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why this matters:&lt;/strong&gt; a UI bug is usually cosmetic severity but high volume. Ten of them in one release feels like a broken product to a user, even though nothing is functionally wrong.&lt;/p&gt;

&lt;h2&gt;
  
  
  Functional defects
&lt;/h2&gt;

&lt;p&gt;The UI looks plausible. The &lt;strong&gt;logic&lt;/strong&gt; is wrong.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A discount applies, but the total does not recalculate&lt;/li&gt;
&lt;li&gt;Removing the last cart item leaves the checkout button enabled&lt;/li&gt;
&lt;li&gt;Sorting by price sorts by string, so &lt;code&gt;£100&lt;/code&gt; comes before &lt;code&gt;£20&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;A "save" button closes the dialog without persisting anything&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The tell: the wrongness exists in application state, not just on screen. Refresh and it is either still wrong (persisted) or back to normal (not persisted) — which is itself diagnostic information worth putting in the report.&lt;/p&gt;

&lt;h2&gt;
  
  
  Validation defects
&lt;/h2&gt;

&lt;p&gt;The system &lt;strong&gt;accepts input it should reject&lt;/strong&gt;, or &lt;strong&gt;rejects input it should accept&lt;/strong&gt;.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Quantity field accepts &lt;code&gt;-3&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Email field accepts &lt;code&gt;test@&lt;/code&gt; with no domain&lt;/li&gt;
&lt;li&gt;A password field accepts 200,000 characters and hangs the form&lt;/li&gt;
&lt;li&gt;A date picker allows a delivery date in the past&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The tell: the defect happens at the boundary between user input and the system, before any business logic runs.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;These are the highest-value bugs to find&lt;/strong&gt; in most web products, because they are cheap to miss and often the entry point for worse problems. A quantity field that accepts negative numbers is a step away from a negative total.&lt;/p&gt;

&lt;h2&gt;
  
  
  Network defects
&lt;/h2&gt;

&lt;p&gt;The UI and the server &lt;strong&gt;disagree&lt;/strong&gt; about what happened.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;POST /cart&lt;/code&gt; returns &lt;code&gt;200&lt;/code&gt;, but the item is not persisted&lt;/li&gt;
&lt;li&gt;A request returns &lt;code&gt;500&lt;/code&gt;, but the UI shows a success toast&lt;/li&gt;
&lt;li&gt;The response includes the right total, but the page renders a hardcoded one&lt;/li&gt;
&lt;li&gt;A request is fired twice (double-submit) because the button was not disabled&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The tell: you have to look. Open DevTools, find the request, compare what the server said to what the screen says. &lt;strong&gt;Every network defect is invisible to a tester who only looks at the screen.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;This is the class most juniors never report, and it is often the most serious — because a UI that lies about server state will eventually corrupt data.&lt;/p&gt;

&lt;h2&gt;
  
  
  A worked example
&lt;/h2&gt;

&lt;p&gt;A discount code fails to apply. Same symptom, four possible diagnoses:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;UI&lt;/strong&gt; — &lt;code&gt;SAVE10&lt;/code&gt; appears in the field but the field's error state is styled invisible. Fix: CSS.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Functional&lt;/strong&gt; — the &lt;code&gt;applyDiscount&lt;/code&gt; reducer runs but does not trigger a total recompute. Fix: state management.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Validation&lt;/strong&gt; — the code is rejected by a regex that excludes codes with digits. Fix: validation rule.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Network&lt;/strong&gt; — &lt;code&gt;POST /discount&lt;/code&gt; returns &lt;code&gt;422 invalid_code&lt;/code&gt; and the UI swallows it. Fix: error handling.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Four different teams, four different fixes, one symptom. &lt;strong&gt;If your report says "discount code doesn't work", all four of those people have to investigate.&lt;/strong&gt; If it says "POST /discount returns 422, UI shows no error", one person fixes it in an hour.&lt;/p&gt;

&lt;h2&gt;
  
  
  Practising classification specifically
&lt;/h2&gt;

&lt;p&gt;Classification is a judgement call, and judgement improves with feedback. The reason it is hard to practise alone is that nobody tells you what the seeded fault actually was.&lt;/p&gt;

&lt;p&gt;That is the specific gap &lt;a href="https://www.bughuntlab.com/" rel="noopener noreferrer"&gt;BughuntLab&lt;/a&gt; fills: each challenge has five seeded faults, and your report is scored on whether you identified the &lt;strong&gt;component&lt;/strong&gt; and &lt;strong&gt;classification&lt;/strong&gt; correctly, against a hidden answer key. Getting the symptom right but the class wrong costs points, which is a fair model of what happens at work.&lt;/p&gt;

&lt;p&gt;You can see the report format in &lt;a href="https://www.bughuntlab.com/how-it-works" rel="noopener noreferrer"&gt;the walkthrough&lt;/a&gt; without signing up for a challenge.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: I build BughuntLab, linked above. The taxonomy and the four-diagnosis example are standard practice and useful independently of any tool.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>testing</category>
    </item>
    <item>
      <title>How to Practise Manual Testing When Nobody Will Hire You Yet</title>
      <dc:creator>Priyanka</dc:creator>
      <pubDate>Wed, 18 Nov 2026 22:02:53 +0000</pubDate>
      <link>https://dev.to/priyanka_desai/how-to-practise-manual-testing-when-nobody-will-hire-you-yet-1j25</link>
      <guid>https://dev.to/priyanka_desai/how-to-practise-manual-testing-when-nobody-will-hire-you-yet-1j25</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://bughuntlab.hashnode.dev/how-to-practise-manual-testing-when-nobody-will-hire-you-yet" rel="noopener noreferrer"&gt;bughuntlab.hashnode.dev&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The QA job market has a specific cruelty: every entry-level role wants experience, and the only way to get experience is a role. Here is how to break that loop without lying on your CV.&lt;/p&gt;

&lt;p&gt;I have reviewed a lot of junior QA applications. The pattern is always the same: a CV that says "experienced in defect reporting" and "knowledge of STLC", and nothing to back either claim up.&lt;/p&gt;

&lt;p&gt;The problem is not the candidate. It is that "manual testing" sounds like something you can learn by reading, when in fact it is a &lt;strong&gt;reporting skill&lt;/strong&gt;. You get better at it the way you get better at writing: by producing work, having it critiqued, and producing more.&lt;/p&gt;

&lt;p&gt;So the question is: where do you get the critique?&lt;/p&gt;

&lt;h2&gt;
  
  
  What practising on a live demo site actually teaches you
&lt;/h2&gt;

&lt;p&gt;The standard advice is "go test a demo e-commerce site". It is better than nothing, but it has a specific ceiling: &lt;strong&gt;nobody tells you if you were right.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;You click around a demo shop, find something odd — a button that does not respond, a total that looks off — and you write it up. But you never learn:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Whether that behaviour was actually a defect or intended&lt;/li&gt;
&lt;li&gt;Whether you classified it correctly&lt;/li&gt;
&lt;li&gt;Whether your severity matched what a real team would assign&lt;/li&gt;
&lt;li&gt;Whether you &lt;em&gt;missed&lt;/em&gt; the three other defects sitting two clicks away&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That last one is the killer. Finding one bug on a demo site feels like success. Finding one bug when five were seeded and you were expected to find all five is a completely different — and much more honest — signal.&lt;/p&gt;

&lt;h2&gt;
  
  
  The three things that actually transfer to a job
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Report structure under time pressure
&lt;/h3&gt;

&lt;p&gt;A real defect report has a fixed shape: title, component, classification, severity, numbered repro steps, expected vs actual. If you are improvising the structure every time, you will be slow on the job. It needs to be automatic.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Classification accuracy
&lt;/h3&gt;

&lt;p&gt;The distinction between a &lt;strong&gt;UI&lt;/strong&gt;, &lt;strong&gt;functional&lt;/strong&gt;, &lt;strong&gt;validation&lt;/strong&gt; and &lt;strong&gt;network&lt;/strong&gt; defect is the single most useful thing a junior tester can learn. A UI bug means the behaviour is right and the rendering is wrong. A network bug means the screen is lying to you about what the server did. These get fixed by different people, in different files.&lt;/p&gt;

&lt;p&gt;Learning to tell them apart is not academic — it is the difference between a ticket that routes itself and a ticket that bounces between three teams.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Knowing when not to file
&lt;/h3&gt;

&lt;p&gt;False positives are a real cost. Every report that turns out to be intended behaviour burns a triage cycle and erodes trust in your future reports. Learning to hesitate — "is this working as designed?" — is a senior instinct that most people develop only after annoying a few teams.&lt;/p&gt;

&lt;h2&gt;
  
  
  Building the loop yourself
&lt;/h2&gt;

&lt;p&gt;If you cannot get a job, build the feedback loop artificially. Three approaches, in order of how much they will actually teach you:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Open-source bug triage.&lt;/strong&gt; Find a project with a lot of open issues and read them. Then try to reproduce them. This teaches you what a &lt;em&gt;real&lt;/em&gt; defect report looks like across dozens of different authors, and whether your own instincts match theirs.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Structured practice labs.&lt;/strong&gt; These are environments with deliberately seeded faults and a known answer key, which gives you the thing a demo site cannot: a score. The scoring is the point — it tells you the difference between "I found a bug" and "I found the bug I was supposed to find, classified correctly."&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Write publicly.&lt;/strong&gt; Publish your reports (anonymised), your testing notes, your checklists. This does two things: it forces clarity, and it becomes a portfolio. A hiring manager who can read three of your actual reports learns more about you than from any CV line.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a portfolio should contain
&lt;/h2&gt;

&lt;p&gt;Not "I know STLC". Instead:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Two or three &lt;strong&gt;full defect reports&lt;/strong&gt;, in your own words, on a real product.&lt;/li&gt;
&lt;li&gt;One &lt;strong&gt;test plan&lt;/strong&gt; for a small feature — scope, out of scope, risks, what you would not bother testing.&lt;/li&gt;
&lt;li&gt;One &lt;strong&gt;bug taxonomy&lt;/strong&gt; piece, if you have written one. It shows you think structurally.&lt;/li&gt;
&lt;li&gt;A short note on &lt;strong&gt;a bug you got wrong&lt;/strong&gt; and what you learned. This is the single most impressive thing a junior can include, and almost nobody does it.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A concrete starting point
&lt;/h2&gt;

&lt;p&gt;If you want the seeded-fault experience — the version where something tells you whether you were right — &lt;a href="https://www.bughuntlab.com/" rel="noopener noreferrer"&gt;BughuntLab&lt;/a&gt; is the lab I built for exactly this. Four working sandbox products, 24 challenges, five seeded faults each, and your report scored against a hidden answer key. A false positive costs 25 points out of 500, which is deliberately the same pressure a real triage meeting puts on you.&lt;/p&gt;

&lt;p&gt;Start with &lt;a href="https://www.bughuntlab.com/how-it-works" rel="noopener noreferrer"&gt;the free walkthrough&lt;/a&gt; rather than paying for anything. If the format does not match how you learn, that is a useful thing to know in two minutes rather than two weeks.&lt;/p&gt;

&lt;p&gt;Whatever you use, the principle is the same: &lt;strong&gt;produce reports, get them judged, produce better reports.&lt;/strong&gt; That loop is the job.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: I build BughuntLab, mentioned above. The advice about portfolios and practice loops is not conditional on using it.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>testing</category>
    </item>
    <item>
      <title>How to Write a Bug Report That Actually Gets Fixed</title>
      <dc:creator>Priyanka</dc:creator>
      <pubDate>Wed, 18 Nov 2026 22:02:24 +0000</pubDate>
      <link>https://dev.to/priyanka_desai/how-to-write-a-bug-report-that-actually-gets-fixed-34dd</link>
      <guid>https://dev.to/priyanka_desai/how-to-write-a-bug-report-that-actually-gets-fixed-34dd</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://bughuntlab.hashnode.dev/how-to-write-a-bug-report-that-actually-gets-fixed" rel="noopener noreferrer"&gt;bughuntlab.hashnode.dev&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;A defect report is not a complaint. It is a reproducible argument that a specific behaviour is wrong. Here is the structure that survives triage.&lt;/p&gt;

&lt;p&gt;Most bug reports die in triage. Not because the bug was fake, but because the report gave the developer nothing to act on. "Checkout is broken" is not a bug report. "Clicking Apply on a discount code silently fails when the cart contains a gift card" is.&lt;/p&gt;

&lt;p&gt;The difference is not writing talent. It is structure.&lt;/p&gt;

&lt;h2&gt;
  
  
  The six fields that matter
&lt;/h2&gt;

&lt;p&gt;Every defect report needs these, in this order. If you can only fill in four, fill in these four.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Title — the observable wrong behaviour, not the suspected cause
&lt;/h3&gt;

&lt;p&gt;Bad: &lt;em&gt;Cart issue&lt;/em&gt;. Better: &lt;em&gt;Discount code rejected when a gift card is in the cart&lt;/em&gt;.&lt;/p&gt;

&lt;p&gt;Never write &lt;em&gt;Fix the reducer&lt;/em&gt; in a title. You do not know that yet, and if you are wrong the developer stops trusting your reports.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Component / area — where in the product
&lt;/h3&gt;

&lt;p&gt;Cart, checkout, search, payments, delivery. Be specific enough that the ticket routes itself.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Classification — what kind of defect it is
&lt;/h3&gt;

&lt;p&gt;This is the field most juniors skip, and it is the one that speeds up triage the most.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Class&lt;/th&gt;
&lt;th&gt;What it means&lt;/th&gt;
&lt;th&gt;Example&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;UI&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Renders wrong, but behaviour is correct&lt;/td&gt;
&lt;td&gt;Price shows &lt;code&gt;£12.500&lt;/code&gt; instead of &lt;code&gt;£12.50&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Functional&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Correct-looking UI, wrong behaviour&lt;/td&gt;
&lt;td&gt;Discount applies but total does not recalculate&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Validation&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Accepts or rejects input it shouldn't&lt;/td&gt;
&lt;td&gt;Quantity field accepts &lt;code&gt;-3&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Network&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Request or response is wrong&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;POST /cart&lt;/code&gt; returns 200, but the item is not persisted&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;A UI bug and a network bug can look identical on screen. Naming the class tells the developer whether to open the component or the API.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Severity — you assign it, and you defend it
&lt;/h3&gt;

&lt;p&gt;Not everything is critical. A misspelled button on the marketing page is not blocking a release; a total that miscounts by a penny is, because it is a money bug and money bugs are legal bugs.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Steps to reproduce — numbered, from a known starting state
&lt;/h3&gt;

&lt;p&gt;Start from a state someone else can reach. "Logged in as a returning customer with one item in the cart" beats "somewhere in checkout".&lt;/p&gt;

&lt;h3&gt;
  
  
  6. Expected vs actual — two sentences, no more
&lt;/h3&gt;

&lt;p&gt;Expected: applying code &lt;code&gt;SAVE10&lt;/code&gt; to a £40 cart yields £36. Actual: the total stays at £40 and no error is displayed.&lt;/p&gt;

&lt;h2&gt;
  
  
  The fields that make it good rather than acceptable
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Evidence.&lt;/strong&gt; A screenshot is fine. A HAR file or a request/response pair is better, because it tells the developer whether the bug is in the browser or the server.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Environment.&lt;/strong&gt; Browser, version, OS, and build. A bug that only reproduces in Safari 17 on mobile is a different bug from one that reproduces everywhere.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Frequency.&lt;/strong&gt; Always / intermittent / once. "Intermittent" is information, not a cop-out — but say how many attempts you made.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A template you can copy
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Title:        Discount code rejected when a gift card is in the cart
Component:    Cart / promotions
Class:        Functional
Severity:     High (money incorrect, no workaround)
Environment:  Chrome 131, macOS 15.1, build 2026.11.18

Preconditions:
  Logged in. Cart contains 1x "Northstar Mug" (£40.00) and 1x gift card (£10.00).

Steps:
  1. Open /cart
  2. Enter discount code SAVE10
  3. Press Apply

Expected: Total becomes £26.00 (10% off £40, gift card applied separately)
Actual:   Total stays at £30.00. No error shown. Network tab shows 200 on POST /cart/discount.

Evidence:  [screenshot] [HAR]
Frequency: Always (5/5 attempts)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That report takes about four minutes to write and saves a developer twenty.&lt;/p&gt;

&lt;h2&gt;
  
  
  The failure mode nobody warns you about: false positives
&lt;/h2&gt;

&lt;p&gt;Here is the uncomfortable part. A report that describes a behaviour that turns out to be &lt;em&gt;intended&lt;/em&gt; is worse than no report at all. It costs the team a triage cycle, it costs you credibility, and it teaches reviewers to skim your tickets.&lt;/p&gt;

&lt;p&gt;Before you file, ask one question: &lt;strong&gt;could this be working as designed?&lt;/strong&gt; If there is a real chance, write it as a question in the team channel first, not as a defect. Then, if it turns out to be a defect, file it properly — with the extra context you just gained.&lt;/p&gt;

&lt;p&gt;Serious test teams score this explicitly. Treating a false positive as a real cost, rather than a harmless over-report, is what separates a tester who gets trusted with the important areas from one who gets their tickets deprioritised.&lt;/p&gt;

&lt;h2&gt;
  
  
  Practising the skill
&lt;/h2&gt;

&lt;p&gt;Reading about report structure does not make you good at it, any more than reading about swimming does. You need reps against something with a known answer.&lt;/p&gt;

&lt;p&gt;That is the specific problem &lt;a href="https://www.bughuntlab.com/" rel="noopener noreferrer"&gt;BughuntLab&lt;/a&gt; was built to solve: four working sandbox products (a storefront, a bank, a crypto wallet, a trading desk), each with five deliberately seeded faults, and your written report scored against a hidden answer key. The scoring is deterministic — component, classification and severity either match or they do not — and a false positive costs points, which is exactly the pressure a real triage meeting applies.&lt;/p&gt;

&lt;p&gt;There is a &lt;a href="https://www.bughuntlab.com/how-it-works" rel="noopener noreferrer"&gt;free walkthrough&lt;/a&gt; if you want to see the report format before committing to a challenge.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: I build BughuntLab. The template above is the one it scores against, which is why I am confident it is the right shape — but the advice stands on its own whether you use the tool or not.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>testing</category>
      <category>qa</category>
    </item>
    <item>
      <title>[Boost]</title>
      <dc:creator>Priyanka</dc:creator>
      <pubDate>Tue, 17 Nov 2026 22:06:21 +0000</pubDate>
      <link>https://dev.to/priyanka_desai/-53fd</link>
      <guid>https://dev.to/priyanka_desai/-53fd</guid>
      <description></description>
    </item>
  </channel>
</rss>
