fix: Add support for custom test command.

[thelukewalton]

This is done so that we can pass 'melos test' from the zeta_flutter monorepo

[Copilot]

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (2)

src/scripts/runTests.ts:13

• Consider using a consistent name for the coverage directory parameter across the codebase (e.g., 'coverageDir' vs 'coverageDirectory' vs 'COVERAGE_DIR') to improve clarity.

export const getTest = async (coverageDir: string, testCommand: string): Promise<stepResponse> => {

README.md:45

• [nitpick] The documentation note regarding 'coverageDir' might be confusing. Consider clarifying that when a custom test-command is provided, the default coverage path is not automatically applied and users should ensure the test command handles coverage accordingly.

Test command is empty by default, and the command used is: `flutter test --coverage --reporter json --coverage-path ${coverageDir}/lcov.info`. This whole string is replaced with the content of test-command, so it is important to consider that `coverageDir` is not provided.