What is idempotency in the context of programming and testing?

Idempotence is a property of an operation or function, meaning that applying it multiple times yields the same result as applying it once. The state of the system after re-executing an idempotent operation does not change compared to after the first execution.

In the context of programming:

Examples of idempotent operations:

• Reading data from a database (GET request), if it does not change the data state.
• Updating a record in a database with a specified value (PUT request to a specific resource with full state).
• Deleting a resource (DELETE request). Repeated deletion of an already deleted resource results in the same state (resource absent).
• Initializing a variable with a specific value.

Examples of non-idempotent operations:

• Adding a new record to a database (POST request). Repeating it will add a new record.
• Incrementing a counter by one.
• Sending an email.

In the context of testing:

Testing for idempotence is important for systems where repeated calls to operations are possible, such as when working with APIs, distributed systems, or messaging systems.

• Test goal: Ensure that re-executing an idempotent operation does not cause undesirable side effects or change the system state beyond what is expected after the first execution.
• Testing methods:
  • Executing the operation N times (N > 1) and checking the system state and result after each execution.
  • Comparing the system state before and after repeated executions (after the first successful one).
  • Checking logs and metrics for anomalies during repeated calls.
• Test case examples:
  • Perform a GET request to a resource 5 times. Ensure that the response data is identical and the resource state on the server has not changed.
  • Perform a PUT request to update a record. Repeat the request. Ensure that the database record remains in the same state after the second request as after the first.
  • Perform a DELETE request to delete a resource. Repeat the request. Ensure that the resource is absent after the first request, and the second request returns the expected status (e.g., 404 Not Found).

Idempotence simplifies error handling and retries, making systems more reliable and predictable, which is a key aspect of quality.