Make hardcoded 15 second launch_testing timeout configurable

[Aposhian]

Feature request

Feature description

Currently you only get 15 seconds to signal ReadyToTest. This is not configurable, which means that you can't use processes that take a long time to startup.

Implementation considerations

Ideally this could be configured at the launch file level. Maybe the tests themselves could say how long they are willing to wait for ReadyToTest?

[clalancette]

Yeah, agreed that this would be nice to make configurable. Please consider making a pull request to do so, we're happy to review.

[jacobperron]

I also hit this hard-coded limit recently. It's easy to reproduce with the following launch test file:

import launch
from launch.actions import TimerAction
import launch_testing.markers
from launch_testing.actions import ReadyToTest


def generate_test_description():
    return launch.LaunchDescription([
        TimerAction(period=16.0, actions=[ReadyToTest()]),
    ])

As a potential workaround, the alternative launch_pytest package does not have such a limit. Here is the equivalent test file written with launch_pytest:

import pytest

import launch
from launch.actions import TimerAction
import launch_pytest
from launch_pytest.actions import ReadyToTest


@launch_pytest.fixture
def launch_description():
    return launch.LaunchDescription([
        TimerAction(period=16.0, actions=[ReadyToTest()]),
    ])


@pytest.mark.launch(fixture=launch_description)
def test_case_1():
    pass

[deepanshubansal01]

Closing the issue, since the feature has been implemented #625