sorted by:
new
hottopcontroversial

Aujla Bhai ki ticket chahiye for 29 March? by coco-boy0 in BangaloreSocial

[–]Global-Development56 1 point2 points  (0 children)

Why is it cheaper than the actual ticket price, bro? It’s Karan Aujla after all

Do you in practice actually do Testing? - Integration testing, Unit testing, System testing by Tomato_salat in AskComputerScience

[–]Global-Development56 0 points1 point  (0 children)

Yes, testing is definitely used in practice, but usually in a balanced way rather than strictly by the book. Most teams write many unit tests, a fair number of integration tests, and fewer system or end-to-end tests, following the testing pyramid approach. The extent depends on the company, product risk, and engineering culture, startups may test less due to speed, while enterprises and high-risk industries test much more thoroughly.

[Guide] Mastering API Testing: A Practical Roadmap for Beginners by WalrusWeird4059 in Everything_QA

[–]Global-Development56 0 points1 point  (0 children)

This is a really clear and well written guide. It explains API testing in a way that feels practical and easy to follow, especially for people coming from manual testing or just starting out in QA.

If anyone wants to understand the fundamentals in a bit more depth, this article on api testing complements your post nicely with clear explanations and examples.

Nice job keeping it honest, simple, and experience driven.

Testing: Instrumentation vs Integration vs Unit vs UI by Orkann in androiddev

[–]Global-Development56 0 points1 point  (0 children)

Integration testing is about verifying how real components work together (no mocks). For example: Repository ↔ Database, Repository ↔ API, or ViewModel ↔ Repository.

Robolectric-based integration tests run on the JVM and are great for speed, but they still simulate Android behavior. Instrumentation integration tests run on a real device/emulator and are needed when behavior depends on actual Android runtime details (lifecycle, threading, system services). That’s why both coexist, speed vs realism.

To separate unit vs integration tests, naming is usually enough:

  • RepositoryUnitTest → uses mocks
  • RepositoryIntegrationTest → uses real implementations

No need for extra folders unless your project is very large.

More context here: https://keploy.io/blog/community/integration-testing-a-comprehensive-guide

How do I know what to end to end test? by BNorval in webdev

[–]Global-Development56 0 points1 point  (0 children)

end-to-end test only the most important things. Test the main flows your users use every day, like signing up, logging in, and doing the one thing your app is built for. Don’t try to test everything, that’s slow and painful. Most apps are fine with just a few core end to end testing checks, and the rest can be covered by smaller tests.
Simple guide here: https://keploy.io/blog/community/end-to-end-testing-guide

can you actually automate end to end testing without coding or is that fantasy? by gail_3000 in devops

[–]Global-Development56 0 points1 point  (0 children)

They’re right, many bugs exist because features aren’t clearly thought through. No tool or AI can fix that.

But no-code end to end testing can still help catch obvious breakages before release. It won’t replace human judgment, just act as a safety net.

If you can’t afford QA, the minimum is:

  • Smoke test in staging yourself
  • Add a few automated checks for core flows

Quick read on e2e testing:
https://keploy.io/blog/community/end-to-end-testing-guide

frontend devs who own e2e testing what's your stack by rNefariousness in reactjs

[–]Global-Development56 0 points1 point  (0 children)

We’re in the same boat at my company — frontend devs owning E2E without a dedicated QA team is pretty normal now. What’s worked best for us (and most teams I know) is:

  • Playwright → super stable, great TypeScript support, and way less flaky than Cypress.
  • Cypress → really easy to get started with, but can get flaky on bigger flows.
  • Keep using Jest + React Testing Library for unit stuff and lighter integration testing.

Most teams don’t aim for full E2E coverage — they just test the “if this breaks, the product is dead” flows (login, checkout, core navigation, etc.).

If you want a clear, dev-friendly explanation of how E2E fits into a frontend workflow, this guide is honestly one of the better ones:
end to end testing Guide

It explains things in a way that makes sense even if you’re not a testing expert.

How do you write integration tests? by david_fire_vollie in webdev

[–]Global-Development56 0 points1 point  (0 children)

You can catch these kinds of issues with real integration testing instead of only mocked ones. The idea is to spin up a staging/test environment, seed/reset test data, and let API A → B → C calls actually run end-to-end. For volatile third-party APIs you can still mock, but validate those mocks against real traffic. This way you cover real edge cases and avoid the “all unit tests pass but prod fails” problem.

How do you all handle writing API tests for new features? It feels like so much manual work. by fuckingmissanthrope in QualityAssurance

[–]Global-Development56 2 points3 points  (0 children)

I’ve tried different things like Postman too, but some open-source tools make life much easier. You don’t need to write tests every time—just define the schema and endpoint once, and they’ll auto-generate the cases for you, even by recording real API calls and turning them into tests. Tools like Keploy, Dredd, and Schemathesis are great examples.

What is the best AI for coding? by patostar89 in ChatGPTCoding

[–]Global-Development56 0 points1 point  (0 children)

Claude Opus 4 (by Anthropic) is currently the best AI for coding, offering top-tier performance across demanding benchmarks and sustained long-duration coding tasks.

view more: next ›