If _send_and_cache() receives a cached response after re-sending an updated request, it should be returned as-is

Check that size updates with bytes added/updated/removed.

Check that size updates with bytes added/updated/removed.

Check that the total bytes are summed up if files are added.

Test approximate expected size of a database, for both file-based and in-memory databases

Test wrapper method for SQLiteDict.sorted(), with all arguments combined

sorted() should handle deserialization errors and not return invalid responses

With stale_if_error, expect to get old cache data if a response has an error status code, that is not in allowable_codes.

With stale_if_error, expect to get the failed response if a response has an error status code, that is in allowable_codes.

With stale_if_error, expect to get old cache data if there is an exception during a request

With stale_if_error as a time value, expect to get old cache data if a response has an error status code AND it is expired by less than the specif

stale_while_revalidate should also apply to normal refresh requests

stale_while_revalidate should also accept a time value (max acceptable staleness)

Just ensure that a subset of relevant attrs get included in the response str; the format may change without breaking the test.

Not much to test for __str__ methods, just make sure they return keys in some format

With sync_index=True, the LRU index should be updated on init for any manual file changes.

Test that total cache size is tracked correctly

DynamoDB's TTL removal process can take up to 48 hours to run, so just test if the 'ttl' attribute is set correctly if enabled, and not set if

Items with no expiry should use SET (no TTL) even when ttl_offset is configured

If there is an error during deserialization, the request should be made again

Conditional request headers should be added if requested by response headers, even if the response is not expired

Conditional request headers should NOT be added if the cached response is not expired and revalidation is otherwise not requested

Conditional request headers should be added if the cached response is expired

Test with Cache-Control response headers

If expiration is 0 and there's a validator, the response should be cached, but with immediate expiration

skip_write should be True when read_only=True or when nothing changed, and False when headers/expiration changed and read_only=False

When updating response headers after revalidating a cached response, don't set both `Content-Length` and `Transfer-Encoding`

If the default is 0, only URLs matching patterns in urls_expire_after should be cached

vacuum() should reclaim disk space after bulk deletion (regression test for #1156)

Check that keys are added.

vary_cache_key should be set when match_headers=True (match all headers)

vary_cache_key should incorporate user match_headers along with Vary headers

Load SQLite cache files created with older versions of requests-cache. Expected behavior: either 1. Serialization format is incompatible, and

Errors from write operations should propagate

Writes to the database acquire the sqlite lock

Acquiring the lock should retry BEGIN IMMEDIATE until it succeeds

Export cached responses as VCR-compatible YAML files (cassettes), split into separate files based on request host Args: cache: Cache

Get all values in the hash