<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>ThinkKit Works</title><description>Practical notes, tools, and workflows for AI, QA Automation, and modern software testing.</description><link>https://thinkkit-works.vercel.app/</link><language>en</language><item><title>Killing Flaky Tests: A Practical Playbook</title><link>https://thinkkit-works.vercel.app/notes/killing-flaky-tests-playbook/</link><guid isPermaLink="true">https://thinkkit-works.vercel.app/notes/killing-flaky-tests-playbook/</guid><description>Flaky tests quietly destroy trust in a test suite. A concrete playbook for finding the flakes, diagnosing the real cause, and stopping them from coming back.</description><pubDate>Fri, 03 Jul 2026 00:00:00 GMT</pubDate><readingTime>2 min read</readingTime><category>QA Automation</category><category>Automation</category><category>Flaky Tests</category><category>Reliability</category><category>CI</category></item><item><title>Reading a Load Test: p95, p99, and Why Averages Lie</title><link>https://thinkkit-works.vercel.app/notes/reading-a-load-test-percentiles/</link><guid isPermaLink="true">https://thinkkit-works.vercel.app/notes/reading-a-load-test-percentiles/</guid><description>How to actually read load-test results — why the average response time hides your worst problems, and how percentiles, throughput, and error rate tell the real story.</description><pubDate>Thu, 02 Jul 2026 00:00:00 GMT</pubDate><readingTime>2 min read</readingTime><category>Performance Testing</category><category>Performance</category><category>Percentiles</category><category>Metrics</category><category>Latency</category></item><item><title>Prompt Patterns for Test Generation That Actually Work</title><link>https://thinkkit-works.vercel.app/notes/prompt-patterns-for-test-generation/</link><guid isPermaLink="true">https://thinkkit-works.vercel.app/notes/prompt-patterns-for-test-generation/</guid><description>Reusable prompt patterns that make an LLM produce useful, structured test cases instead of vague suggestions — with the guardrails that keep it honest.</description><pubDate>Wed, 01 Jul 2026 00:00:00 GMT</pubDate><readingTime>2 min read</readingTime><category>AI for QA</category><category>AI</category><category>Prompting</category><category>Test Design</category><category>Patterns</category></item><item><title>AI-assisted Defect Analysis for QA Teams</title><link>https://thinkkit-works.vercel.app/notes/ai-assisted-defect-analysis-for-qa-teams/</link><guid isPermaLink="true">https://thinkkit-works.vercel.app/notes/ai-assisted-defect-analysis-for-qa-teams/</guid><description>Using AI to speed up defect analysis — clustering duplicate reports, suggesting likely root-cause areas, and drafting reproduction steps — without outsourcing judgment.</description><pubDate>Tue, 30 Jun 2026 00:00:00 GMT</pubDate><readingTime>2 min read</readingTime><category>AI for QA</category><category>AI</category><category>Defect Analysis</category><category>Root Cause</category><category>Triage</category></item><item><title>How I Use AI to Generate QA Test Cases</title><link>https://thinkkit-works.vercel.app/notes/how-i-use-ai-to-generate-qa-test-cases/</link><guid isPermaLink="true">https://thinkkit-works.vercel.app/notes/how-i-use-ai-to-generate-qa-test-cases/</guid><description>A repeatable workflow for turning a requirement or user story into positive, negative, and edge-case test cases with an LLM — without letting the model invent coverage.</description><pubDate>Sun, 28 Jun 2026 00:00:00 GMT</pubDate><readingTime>2 min read</readingTime><category>AI for QA</category><category>AI</category><category>Test Design</category><category>Prompting</category><category>Coverage</category></item><item><title>Finding Bottlenecks: A Systematic Approach to Performance Debugging</title><link>https://thinkkit-works.vercel.app/notes/finding-performance-bottlenecks/</link><guid isPermaLink="true">https://thinkkit-works.vercel.app/notes/finding-performance-bottlenecks/</guid><description>A repeatable method for locating the real bottleneck in a slow system — measure before you guess, follow the resource, and confirm the fix instead of hoping.</description><pubDate>Sat, 27 Jun 2026 00:00:00 GMT</pubDate><readingTime>3 min read</readingTime><category>Performance Testing</category><category>Performance</category><category>Bottleneck</category><category>Profiling</category><category>Debugging</category></item><item><title>QA Automation Roadmap for Modern Teams</title><link>https://thinkkit-works.vercel.app/notes/qa-automation-roadmap-for-modern-teams/</link><guid isPermaLink="true">https://thinkkit-works.vercel.app/notes/qa-automation-roadmap-for-modern-teams/</guid><description>A phased roadmap for growing test automation from a fragile pilot into a maintained, CI-integrated suite that the whole team trusts.</description><pubDate>Fri, 26 Jun 2026 00:00:00 GMT</pubDate><readingTime>2 min read</readingTime><category>QA Automation</category><category>Automation</category><category>Strategy</category><category>CI/CD</category><category>Roadmap</category></item><item><title>A Mobile Release Testing Checklist</title><link>https://thinkkit-works.vercel.app/notes/mobile-release-testing-checklist/</link><guid isPermaLink="true">https://thinkkit-works.vercel.app/notes/mobile-release-testing-checklist/</guid><description>A practical pre-release checklist for mobile apps — the device, network, lifecycle, and store-readiness checks that catch the bugs desktop testing never will.</description><pubDate>Thu, 25 Jun 2026 00:00:00 GMT</pubDate><readingTime>2 min read</readingTime><category>Mobile Testing</category><category>Mobile</category><category>Release</category><category>Checklist</category><category>Android</category><category>iOS</category></item><item><title>Swagger to Test Case: My QA Workflow</title><link>https://thinkkit-works.vercel.app/notes/swagger-to-test-case-workflow/</link><guid isPermaLink="true">https://thinkkit-works.vercel.app/notes/swagger-to-test-case-workflow/</guid><description>How I turn an OpenAPI/Swagger spec into a prioritized set of API test cases and a runnable Postman collection, without hand-writing every request.</description><pubDate>Wed, 24 Jun 2026 00:00:00 GMT</pubDate><readingTime>2 min read</readingTime><category>API Testing</category><category>Swagger</category><category>OpenAPI</category><category>Postman</category><category>API</category></item><item><title>Risk-Based Testing: Where to Focus Limited Time</title><link>https://thinkkit-works.vercel.app/notes/risk-based-testing-where-to-focus/</link><guid isPermaLink="true">https://thinkkit-works.vercel.app/notes/risk-based-testing-where-to-focus/</guid><description>You can never test everything. Risk-based testing is a practical method for spending your limited testing time where a failure would hurt most.</description><pubDate>Mon, 22 Jun 2026 00:00:00 GMT</pubDate><readingTime>2 min read</readingTime><category>Testing Strategy</category><category>Strategy</category><category>Risk</category><category>Prioritization</category><category>Coverage</category></item><item><title>Designing a Maintainable Test Automation Framework</title><link>https://thinkkit-works.vercel.app/notes/designing-a-maintainable-test-automation-framework/</link><guid isPermaLink="true">https://thinkkit-works.vercel.app/notes/designing-a-maintainable-test-automation-framework/</guid><description>The structural decisions — page objects, fixtures, config layering, and reporting — that keep a test framework maintainable as it grows past a few hundred tests.</description><pubDate>Sat, 20 Jun 2026 00:00:00 GMT</pubDate><readingTime>2 min read</readingTime><category>QA Automation</category><category>Framework</category><category>Page Object</category><category>Fixtures</category><category>Maintainability</category></item><item><title>A Definition of Done for QA</title><link>https://thinkkit-works.vercel.app/notes/definition-of-done-for-qa/</link><guid isPermaLink="true">https://thinkkit-works.vercel.app/notes/definition-of-done-for-qa/</guid><description>A practical Definition of Done that bakes quality into every story — so &quot;done&quot; means shippable, not just &quot;the code compiles on my machine.&quot;</description><pubDate>Fri, 19 Jun 2026 00:00:00 GMT</pubDate><readingTime>2 min read</readingTime><category>Testing Strategy</category><category>Strategy</category><category>Definition of Done</category><category>Process</category><category>Quality</category></item><item><title>Robot Framework Notes for API Testing</title><link>https://thinkkit-works.vercel.app/notes/robot-framework-notes-for-api-testing/</link><guid isPermaLink="true">https://thinkkit-works.vercel.app/notes/robot-framework-notes-for-api-testing/</guid><description>Practical notes on using Robot Framework with the RequestsLibrary for readable, maintainable API tests that non-developers can still follow.</description><pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate><readingTime>1 min read</readingTime><category>API Testing</category><category>Robot Framework</category><category>API</category><category>Automation</category><category>Keywords</category></item><item><title>Load, Stress, Soak, Spike: Choosing the Right Performance Test</title><link>https://thinkkit-works.vercel.app/notes/load-stress-soak-spike-test-types/</link><guid isPermaLink="true">https://thinkkit-works.vercel.app/notes/load-stress-soak-spike-test-types/</guid><description>The four performance test types answer four different questions. A practical guide to when to run each one, and what a passing result actually tells you.</description><pubDate>Tue, 16 Jun 2026 00:00:00 GMT</pubDate><readingTime>2 min read</readingTime><category>Performance Testing</category><category>Performance</category><category>Load Testing</category><category>Stress Testing</category><category>Soak Testing</category></item><item><title>The Test Pyramid in Practice</title><link>https://thinkkit-works.vercel.app/notes/the-test-pyramid-in-practice/</link><guid isPermaLink="true">https://thinkkit-works.vercel.app/notes/the-test-pyramid-in-practice/</guid><description>The test pyramid is a useful heuristic that is easy to misread. A practical look at what each layer is for, and how to keep the shape from inverting.</description><pubDate>Tue, 16 Jun 2026 00:00:00 GMT</pubDate><readingTime>2 min read</readingTime><category>Testing Strategy</category><category>Strategy</category><category>Test Pyramid</category><category>Unit</category><category>E2E</category></item><item><title>Building an Internal QA Knowledge Base with AI</title><link>https://thinkkit-works.vercel.app/notes/building-an-internal-qa-knowledge-base-with-ai/</link><guid isPermaLink="true">https://thinkkit-works.vercel.app/notes/building-an-internal-qa-knowledge-base-with-ai/</guid><description>How to turn scattered test notes, bug patterns, and tribal knowledge into a searchable QA knowledge base — and where AI genuinely helps versus where it gets in the way.</description><pubDate>Sun, 14 Jun 2026 00:00:00 GMT</pubDate><readingTime>2 min read</readingTime><category>Tools &amp; Workflow</category><category>Knowledge Base</category><category>AI</category><category>Documentation</category><category>Workflow</category></item><item><title>Writing Bug Reports Developers Love</title><link>https://thinkkit-works.vercel.app/notes/writing-bug-reports-developers-love/</link><guid isPermaLink="true">https://thinkkit-works.vercel.app/notes/writing-bug-reports-developers-love/</guid><description>A good bug report gets fixed fast; a vague one bounces back and forth for days. The anatomy of a report that a developer can act on immediately.</description><pubDate>Sat, 13 Jun 2026 00:00:00 GMT</pubDate><readingTime>2 min read</readingTime><category>Tools &amp; Workflow</category><category>Workflow</category><category>Bug Reports</category><category>Communication</category><category>Process</category></item><item><title>JMeter vs k6: When I Use Each Tool</title><link>https://thinkkit-works.vercel.app/notes/jmeter-vs-k6/</link><guid isPermaLink="true">https://thinkkit-works.vercel.app/notes/jmeter-vs-k6/</guid><description>A practical comparison of JMeter and k6 for load testing — not a winner-takes-all verdict, but a decision guide based on team skills, protocols, and CI needs.</description><pubDate>Fri, 12 Jun 2026 00:00:00 GMT</pubDate><readingTime>2 min read</readingTime><category>Performance Testing</category><category>JMeter</category><category>k6</category><category>Load Testing</category><category>Performance</category></item><item><title>Performance Testing Checklist Before Release</title><link>https://thinkkit-works.vercel.app/notes/performance-testing-checklist-before-release/</link><guid isPermaLink="true">https://thinkkit-works.vercel.app/notes/performance-testing-checklist-before-release/</guid><description>A practical pre-release checklist to confirm a performance test will produce trustworthy results — environment parity, data, SLAs, and monitoring — before you generate load.</description><pubDate>Wed, 10 Jun 2026 00:00:00 GMT</pubDate><readingTime>2 min read</readingTime><category>Performance Testing</category><category>Performance</category><category>Load Testing</category><category>Checklist</category><category>Release</category></item><item><title>A Repeatable Bug Triage Workflow</title><link>https://thinkkit-works.vercel.app/notes/a-repeatable-bug-triage-workflow/</link><guid isPermaLink="true">https://thinkkit-works.vercel.app/notes/a-repeatable-bug-triage-workflow/</guid><description>A simple, repeatable workflow for triaging incoming bugs so nothing important gets lost and nothing trivial blocks a release.</description><pubDate>Mon, 08 Jun 2026 00:00:00 GMT</pubDate><readingTime>2 min read</readingTime><category>Tools &amp; Workflow</category><category>Triage</category><category>Workflow</category><category>Process</category><category>Bug Tracking</category></item><item><title>Root Detection Testing Checklist for Android Apps</title><link>https://thinkkit-works.vercel.app/notes/root-detection-testing-checklist-android/</link><guid isPermaLink="true">https://thinkkit-works.vercel.app/notes/root-detection-testing-checklist-android/</guid><description>A practical checklist for verifying that an Android app&apos;s root and tamper detection actually works — and holds up against common bypass techniques.</description><pubDate>Sat, 06 Jun 2026 00:00:00 GMT</pubDate><readingTime>2 min read</readingTime><category>Mobile Testing</category><category>Android</category><category>Security</category><category>Root Detection</category><category>Mobile</category></item><item><title>Real Devices vs Emulators for Mobile Testing</title><link>https://thinkkit-works.vercel.app/notes/real-devices-vs-emulators-for-mobile-testing/</link><guid isPermaLink="true">https://thinkkit-works.vercel.app/notes/real-devices-vs-emulators-for-mobile-testing/</guid><description>When to test on emulators, when you need real devices, and how to build a device strategy that balances coverage against cost.</description><pubDate>Thu, 04 Jun 2026 00:00:00 GMT</pubDate><readingTime>2 min read</readingTime><category>Mobile Testing</category><category>Mobile</category><category>Devices</category><category>Emulators</category><category>Coverage</category></item><item><title>Postman Collection Strategy for API Regression</title><link>https://thinkkit-works.vercel.app/notes/postman-collection-strategy-for-api-regression/</link><guid isPermaLink="true">https://thinkkit-works.vercel.app/notes/postman-collection-strategy-for-api-regression/</guid><description>How to structure Postman collections and environments so an API regression suite stays fast, readable, and runnable in CI with Newman.</description><pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate><readingTime>2 min read</readingTime><category>API Testing</category><category>Postman</category><category>Newman</category><category>Regression</category><category>CI</category></item></channel></rss>