Skip to content

Conversation

Guldem
Copy link
Member

@Guldem Guldem commented Jul 1, 2025

  • Update dependencies
    • Update very_good_analysis to 10.0.0
    • Update test to 1.26.2
    • Update meta to 1.16.0
    • Updated stack_trace to 1.12.1
    • Added topics: [test, testing, parameterized] to pubspec.yaml
    • Added small explanation to README.md about Future.error usage in tests. Closes Testing with Future.error #23
    • Updated dart formatting.

Updates included from #25

README.md Outdated
```

### Testing with `Future.error` values
When using `Future.error` directly in your parameterized test values, this might leads to not executing tests at all. In order to handle this correctly your can provide the `Future` as a callback function.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NIT: might leads -> might lead

@Guldem Guldem merged commit a314870 into main Oct 1, 2025
1 check passed
@Guldem Guldem deleted the chore/updates branch October 1, 2025 11:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Testing with Future.error

2 participants