Testing/E2E: Guides and Practical Know-how | Page 22 | mironsoft Blog
Testing/E2E
-
Jan 21, 2025
GraphQL authorization does not end at the query check. Sensitive fields such as email addresses, order histories, and admin-specific data must be secured at the field level, inside the resolver context, not just in the schema. This article shows how that works in practice.
-
Jan 20, 2025
A load test simulating a high number of concurrent users over five minutes only confirms that a system can handle that load briefly, but says nothing about what happens once the same, moderate load continues uninterrupted for twelve or twenty-four hours. That's exactly the question a soak test (also called an endurance test) answers, sustaining a realistic but constant load over a considerably longer period, to uncover creeping problems like memory leaks, slowly exhausted resource pools, or uncontrolled log file growth before they suddenly strike in production after hours of seemingly stable operation.
-
Jan 11, 2025
Performance regressions rarely come from one dramatic change, they accumulate from many small degradations that each stay under the radar. A CI pipeline that automatically compares bundle size and Lighthouse metrics against the base branch on every pull request makes this slow decline visible before it reaches the main branch and production.
-
Jan 11, 2025
A high coverage number feels reassuring, but it often says little about whether your tests actually catch bugs. This article explains what line, branch, and path coverage really measure, why coverage is only a floor and not a quality goal, and how to set realistic, risk based targets for unit, integration, and E2E tests.
-
Jan 10, 2025
A Vue/Nuxt checklist for launch is more than a to-do list, it is the structured quality gate that prevents an app from going into production with slow Core Web Vitals, missing accessibility, or a fragile API integration.
-
-
Jan 7, 2025
Device emulation in Cypress and Playwright simulates viewport, user agent, and touch events in seconds, giving fast feedback in every CI pipeline. What stays invisible is real GPU and CPU constraints, real mobile network latency, and the rendering quirks of Safari on iOS. This article shows exactly when emulation is enough and when real-device cloud testing via BrowserStack or Sauce Labs becomes essential.
-
Jan 6, 2025
A separate document describing a test suite's purpose and structure feels helpful the moment it's written, but in practice almost inevitably goes stale within a few months, once the described test code keeps evolving while the document itself stays frozen. The most effective form of test documentation is therefore not a separate, independently maintained document, but the test code itself, provided it's written so it reveals its own intent without any additional explanation.
-
Jan 4, 2025
Every plugin increases memory usage, extends startup time, and can slow the IDE down. The question is not which plugins exist, but which ones genuinely add value to your own workflow, and which ones can be disabled without any loss.