-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
filter
function is not executed by test
#29
Comments
This wouldn't support async filters and it doesn't pass the proper arguments. Given we're mocking inquirer, not running any settings function made sense for us. |
The The thing is that I was refactoring a filter function and wanted to test if it worked correctly. For instance, In my I just wanted to make sure if this was on purpose or not. I can always take a look to do a PR. But it's your call to make off course :). |
Yeah it was weird when I found this issue, I can't replicate fully the generator behavior in a testing environment |
Any chance of getting this fixed? I was surprised and disappointed to see that the filter is completely ignored. |
This issue is stale because it has been open 15 days with no activity. Remove stale label or comment or this will be closed in 5 days |
Only 15 days?? 🤣🤣🤣 |
@marcofugaro you just found a bug, please report at https://github.com/yeoman/yeoman-test/issues/new The relevant part is: yeoman-test/.github/workflows/stale.yml Lines 13 to 15 in 46c5183
Just kidding, I am cleaning up irrelevant old issues. About this issue, I don't now much about inquirer:
But added a way to workaround it at #73 |
Test cases are controlled environment. |
What is the proper way of testing |
I noticed that the filter is not being executed by the tester. I changed this line to
And now everything seems to be working as expected. Not sure if it's that easy to fix though.
The text was updated successfully, but these errors were encountered: