Mocking APIs using WireMock for testing negative cases when it is not possible to change the API behaviour
WireMock lets you produce failures a real API will not give you on demand: timeouts, 500s, malformed bodies.
Newest first. 300 load testing, JMeter, test automation and monitoring guides, plus tool comparisons. Browse by topic from the blog home.
WireMock lets you produce failures a real API will not give you on demand: timeouts, 500s, malformed bodies.
Categories let one suite be sliced by speed or area, so CI can run the fast set per commit.
The closer the parity, especially in data and scale, the more useful it is. A staging environment that drifts from production gives false confidence.
Compare the same viewport and state, or the diff is dominated by noise. Review differences rather than gating on pixel equality, which fails constantly.
Image comparison catches visual breakage that assertions never check for. Run in a consistent environment; a different OS produces different pixels.
linkText matches the full visible text; partialLinkText matches a substring.
Exchanges fail at the order book and matching engine, not at the marketing pages.
Puppeteer captures viewport, full-page or single-element screenshots.
A campaign delivers its traffic in minutes, which is a spike rather than a load curve.
Pixel comparison catches visual regressions that functional tests never assert on. Set a tolerance, or antialiasing and fonts will fail every run.
A screen recording captures the exact sequence that reproduces a bug, which a description rarely does.
Debugging transpiled code needs source maps, or breakpoints land on the wrong lines.
A proxy between the device and the network is the only reliable way to see native app traffic.
The WebDriver Sampler measures real browser rendering, which HTTP samplers cannot see. Use it to measure front-end timing, not to generate volume.
A DataProvider feeds many input sets into one test method, which keeps cases out of the code.
Two ways to save Apache JMeter results: the -l flag with jmeter.save.saveservice properties for CSV, or XML for the full sample detail. With examples.
Opening a tab is only half the job; you must switch the driver to the new window handle. Track handles before and after, then switch to the difference.
Backgrounding and resuming is where state bugs surface, so it belongs in the test suite. Verify state after resume, not just that the app reopened.
Explicit waits target a condition; implicit waits apply a blanket timeout to every lookup.
Appium reaches the Android system buttons through key events rather than element clicks.
Wrap the literal in double quotes instead, which is the simplest fix. Use concat() when the text contains both quote characters.
findElements with By.tagName("a") returns every anchor, including ones that are not visible.
A 500 means the server failed, so the answer is in its logs rather than the request.
Hover needs the Actions class; a plain click will not trigger CSS or JS hover states.
Don’t miss out on the latest testing tips and tricks, tools and news related to software testing.
Already +20,000 members in the list.
Load test websites and APIs from 25 cloud regions, monitor page speed and uptime, and get AI analysis that explains your results in plain English.