Skip to content

unit

Directory actions

More options

Directory actions

More options

Latest commit

 

History

History

unit

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
README.md
README.md
 
 
__init__.py
__init__.py
 
 
conftest.py
conftest.py
 
 
test_actor_start_params.py
test_actor_start_params.py
 
 
test_client_errors.py
test_client_errors.py
 
 
test_client_headers.py
test_client_headers.py
 
 
test_client_pagination.py
test_client_pagination.py
 
 
test_client_request_queue.py
test_client_request_queue.py
 
 
test_client_timeouts.py
test_client_timeouts.py
 
 
test_dataset_list_items.py
test_dataset_list_items.py
 
 
test_http_clients.py
test_http_clients.py
 
 
test_logging.py
test_logging.py
 
 
test_pluggable_http_client.py
test_pluggable_http_client.py
 
 
test_postprocess_generated_models.py
test_postprocess_generated_models.py
 
 
test_run_charge.py
test_run_charge.py
 
 
test_statistics.py
test_statistics.py
 
 
test_storage_collection_listing.py
test_storage_collection_listing.py
 
 
test_url_generation.py
test_url_generation.py
 
 
test_utils.py
test_utils.py
 
 

README.md

Unit tests

Unit tests must be fully isolated from the real Apify API. Use mocks, fakes, or a local HTTP test server.

They must not require:

  • production or test API tokens
  • network access at all

Any test that calls the Apify API belongs to integration tests.