Open steve-bate opened 2 days ago
Are you running this from the right directory? File tests/feditests/mastodon_saas_api.json
does seem to exist on develop
.
-v
and -v -v
should continue to exist.
Are you running this from the right directory?
You'll need to tell me the "right" directory to answer that question. ;-) I'm running from the project root directory (the parent of tests
).
I don't see the verbose option for the run command:
10:28 $ feditest run --help
usage: feditest run [-h] [--testsdir [TESTSDIR ...]] [--testplan TESTPLAN] [--nodedriversdir NODEDRIVERSDIR]
[--domain DOMAIN] [--interactive] [--who] [--tap [TAP]] [--html HTML] [--template TEMPLATE]
[--json [JSON]] [--summary [SUMMARY]]
options:
-h, --help show this help message and exit
--testsdir [TESTSDIR ...]
Directory or directories where to find tests
--testplan TESTPLAN Name of the file that contains the test plan to run
--nodedriversdir NODEDRIVERSDIR
Directory or directories where to find extra drivers for nodes that can be tested
--domain DOMAIN Local-only DNS domain for the DNS hostnames that are auto-generated for nodes
--interactive Run the tests interactively
--who Record who ran the test plan on what host.
--tap [TAP] Write results in TAP format to stdout, or to the provided file (if given).
--json [JSON], --testresult [JSON]
Write results in JSON format to stdout, or to the provided file (if given).
--summary [SUMMARY] Write summary to stdout, or to the provided file (if given). This is the default if no other output
option is given
html:
HTML options
--html HTML Write results in HTML format to the provided file.
--template TEMPLATE When specifying --html, use this template (defaults to 'default').
However, later I saw it is at the feditest
command level. Unfortunately, it didn't have the desired effect and only the terse errors message was shown. Seems like I'll need to dig into the code to diagnose the issue.
It's on feditest
itself, not the sub-command run
. So feditest -v run ...
is the winning ticket ...
The above command should work in the root directory of the feditest
repo.
Yeah, like I said, the -v
on Feditest still doesn't show a stack trace for the error. I'm running from the project root.
I'll debug it when I'm back from my trip.
Moved from PR #333 for further discussion.
I know there was the "or such" disclaimer, but when I run that command I see:
The 'tests/feditests/mastodon_saas_api.json' exists relative to the feditest base directory so I don't know what happening yet. Was the verbose option (that included stack traces) removed? That would help in these cases to know which code to explore to determine the cause of the error.