Make tests compile and run faster
# Use case According to [flutter.dev](https://flutter.dev/) one of the things flutter aims at is fast development. I think being able to develop in a TDD workflow contributes to this goal. In our case, we have suite about 500 tests, consisting of unit and widget tests. In order to facilitate a real TDD workflow, all the tests should run very fast. There are some sources that suggest a maximum executing time of less than 10s: https://blog.ploeh.dk/2012/05/24/TDDtestsuitesshouldrunin10secondsorless/#:~:text=The%20test%20suite%20you%20work,be%20faster%20than%2010%20milliseconds. Currently, our test suite is executing in about **2min**, which makes the TDD approach very hard, because it disrupts your workflow (better described in the article). # Proposal The aim of this ticket is more to collect all the tickets, that would contribute to a better TDD experience. So please add additional things that prevent you from a good TDD experience. ## Live Unit Testing https://github.com/flutter/flutter/issues/4719 https://github.com/Dart-Code/Dart-Code/issues/2878 ## Improve Performance of Tests https://github.com/flutter/flutter/issues/17130 https://github.com/dart-lang/sdk/issues/32953 ## Hot Reload for Unit Tests https://github.com/flutter/flutter/issues/25973 https://github.com/szotp/hottie/ Please consider 👍 this and linked tickets if you thing this is important.
Posted by HerrNiklasRaab on Oct 30, 2020, 7:12 PM
Tags
Related issues
Raise real-world problems, find people facing the same issue, and discuss solutions.3,000 issues0 comments
github (E-commerce)
proposal: cmd/cgo: cgo without a C toolchain
Replace PowerToys Run with Command Palette
VPS with a vRack leg
Possibility of Portal 1 Code Inclusion
Introducing NewPlayer
Metrics for PRs are never expiring ("memory leak")
ship even more of the compiler in source form
Flatpak Application TRACKING ISSUE
Make tests compile and run faster
# Use case According to [flutter.dev](https://flutter.dev/) one of the things flutter aims at is fast development. I think being able to develop in a TDD workflow contributes to this goal. In our case, we have suite about 500 tests, consisting of unit and widget tests. In order to facilitate a real TDD workflow, all the tests should run very fast. There are some sources that suggest a maximum executing time of less than 10s: https://blog.ploeh.dk/2012/05/24/TDDtestsuitesshouldrunin10secondsorless/#:~:text=The%20test%20suite%20you%20work,be%20faster%20than%2010%20milliseconds. Currently, our test suite is executing in about **2min**, which makes the TDD approach very hard, because it disrupts your workflow (better described in the article). # Proposal The aim of this ticket is more to collect all the tickets, that would contribute to a better TDD experience. So please add additional things that prevent you from a good TDD experience. ## Live Unit Testing https://github.com/flutter/flutter/issues/4719 https://github.com/Dart-Code/Dart-Code/issues/2878 ## Improve Performance of Tests https://github.com/flutter/flutter/issues/17130 https://github.com/dart-lang/sdk/issues/32953 ## Hot Reload for Unit Tests https://github.com/flutter/flutter/issues/25973 https://github.com/szotp/hottie/ Please consider 👍 this and linked tickets if you thing this is important.
Comments (0)
No comments yet. Start the discussion.