-
Notifications
You must be signed in to change notification settings - Fork 421
Commit
- Fixes #632 - Removing string comparison tests. These are not useful and are extremely burdensome. - Regenerating mocks using new mock generation logic. Renaming mocks, adding config for recursive generation Adding a fixture for in-package recursive generation. I added config in .mockery.yaml for this to test that mockery doesn't re-generate interfaces it has created. I need to add an explicit integration test for this. Add end-to-end tests
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
#!/bin/bash | ||
SCRIPT_DIR=$( cd -- "$( dirname -- "${BASH_SOURCE[0]}" )" &> /dev/null && pwd ) | ||
|
||
for file in $(ls $SCRIPT_DIR/test_*.sh); do | ||
$file | ||
done |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
#!/bin/bash | ||
# This tests https://github.com/vektra/mockery/issues/632, where | ||
# mockery was generating mocks of its own auto-generated code. | ||
|
||
echo "==========" | ||
echo "RUNNING $0" | ||
echo "==========" | ||
|
||
# New mocks may legimitately be created, so we run mockery once first | ||
go run . | ||
num_files_before=$(find . -type f | wc -l) | ||
go run . | ||
num_files_after=$(find . -type f | wc -l) | ||
|
||
if [ $num_files_before -ne $num_files_after ]; then | ||
echo "ERROR: detected increased file count over multiple mockery runs." | ||
echo "before: $num_files_before. after: $num_files_after" | ||
exit 1 | ||
fi | ||
echo "SUCCESS: identical number of files over multiple mockery runs" | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
#!/bin/bash | ||
|
||
echo "==========" | ||
echo "RUNNING $0" | ||
echo "==========" | ||
|
||
go run . | ||
rt=$? | ||
if [ $rt -ne 0 ]; then | ||
echo "ERROR: non-zero return code from mockery" | ||
exit 1 | ||
fi | ||
echo "SUCCESS: successfully generated mocks defined in .mockery.yaml" |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.