Category: community

  • What Is Resilience Testing? Types, Tools & Examples

    What Is Resilience Testing? Types, Tools & Examples

    Resilience testing checks whether software keeps serving users when a dependency breaks. Teams inject timeouts, error responses, and slow databases, then measure the impact and the time to recover. Keploy brings this into CI: its recorded mocks can be edited into failure responses and replayed on every pull request. Resilience testing gets skipped for the…

    —

    by

    in
  • Functional vs non-functional testing explained

    Functional vs non-functional testing explained

    Functional testing checks what a system does: whether each feature behaves the way the requirements say. Non-functional testing checks how well it does it: how fast, how secure, how stable under load and how easy to use. A login that accepts the right password passes functional testing. A login that takes eight seconds to respond…

    —

    by

    in
  • What is a mock server? How it works, setup and tools

    What is a mock server? How it works, setup and tools

    A mock server answers your app’s API calls with responses you control, so you can build and test without waiting on the real backend. Here is how it works and how to set one up.

    —

    by

    in
  • What Is a Regression Bug? Causes and Real Examples

    What Is a Regression Bug? Causes and Real Examples

    Regression bug reports tend to share one sentence: it worked last week. That sentence makes them some of the most frustrating tickets to receive, because the feature was tested, shipped, and trusted before something unrelated knocked it over. Users also feel them sooner than most bugs, since they were already relying on the thing that…

    —

    by

    in
  • Functional vs regression testing: Key differences

    Functional vs regression testing: Key differences

    Functional testing checks that a feature works the way the requirements say. Regression testing checks that features which already worked still work after a code change. Put simply, functional testing asks "does this work?" and regression testing asks "did we just break something?" The two get mixed up because they often use the same test…

    —

    by

    in
  • Automated functional testing: How it works and tools

    Automated functional testing: How it works and tools

    Automated functional testing means using scripts or tools to check that each feature of an application does what the requirements say, without a person clicking through every step. The tool sends the inputs, compares the result with what was expected and flags anything that breaks, on every build if you want it to. That is…

    —

    by

    in
  • API Regression Testing: Catch Breaking Changes Early

    API Regression Testing: Catch Breaking Changes Early

    API regression testing re-runs your API tests after every code change so existing endpoints keep returning what clients expect. A solid setup checks response shapes, auth, and latency, mocks external dependencies, and runs a fast suite on each pull request with the full suite nightly. Keploy, an open-source tool, generates that suite and its dependency…

    —

    by

    in
  • Regression Testing vs Integration Testing: Key Differences

    Regression Testing vs Integration Testing: Key Differences

    Here is a situation most backend teams have lived through. A developer changes how the user service formats dates. It is a tiny change: one line, a cleaner ISO format, every unit test still green. The pull request gets approved in five minutes. Two days later, the billing service starts failing to generate invoices, because…

    —

    by

    in
  • Integration Testing vs Functional Testing: Key Differences

    Integration Testing vs Functional Testing: Key Differences

    Ask five engineers whether a test is "functional" or "integration" and you will probably get three answers. That is not because people are confused. It is because the same test can honestly be both. Here is the short version. Integration testing checks that components work together. Functional testing checks that the software does what the…

    —

    by

    in
  • Regression Testing in Agile: Test Every Sprint Without Slowing Down

    Regression Testing in Agile: Test Every Sprint Without Slowing Down

    Regression testing in agile happens inside every sprint, alongside the stories being built. Targeted tests run on each pull request, the full suite runs before sprint review and every release, and hotfixes get a check of their own. The whole team shares the work while one tester curates the suite, and it stays fast when…

    —

    by

    in