Skip to content

utils.is_url_connectable should take a URL? #3904

@sethamclean

Description

@sethamclean

I am starting a docker container using the image 'selenium/standalone-chrome' as part of my integration tests. If tests run immediately they fail due to the service apparently not being ready. This can be resolved by using utils.is_url_connectable. However this container may not necessarily be on the local system.

utils.is_connectable seems like a good alternative, but it doesn't seem to check the /status URL and the service seems to not be ready even when this returns True.

Additionally the function name is_url_connectable seems strange given only a port can be provided as an argument.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions