Thank you for your video. It was very helpful and gives me more confidence to do testing in Flutter. Even if you told me the same info from flutter dev documentation. It makes more sense now!!
Oo, missed opportunity to link to your other testing videos in the description + video annotation. I know we can just search, but that was the first thing I looked for when you mentioned it at the beginning of the video.
Is there a best practice in Flutter for using a test database for integration testing? This is a nice introduction to integration testing, but I'd never want to use the primary production database for testing.
How to click on the checkbox showing over there? Please help me as I need to click on favorite button showing in grid view and I am unable to access it. Looking forward to your response.
Info given by ChatGPT4: As of my knowledge cutoff in September 2021, `flutter_driver` has been the traditional way of writing integration tests for Flutter apps. However, Flutter announced the `integration_test` package as the new way of testing, which is easier and more consistent with widget tests. Here are some differences and advantages between the two: 1. **Driver vs In-Process:** `flutter_driver` runs tests in a separate process, and communicates with the app-under-test over a JSON wire protocol. This can sometimes introduce complications with setup, latency, or issues with flakiness. On the other hand, `integration_test` runs the tests in the same process as the app, resulting in faster execution and simpler setup. 2. **Test Writing:** `flutter_driver` requires a more complex setup where you often end up with two separate files: one for the test app and another for the test scripts. With `integration_test`, the setup is simpler and the test code is more similar to unit and widget tests. 3. **Host Platform Support:** `integration_test` has broader support for running tests directly on different host platforms, including macOS, Windows, Linux, Web, Chrome, etc., as it doesn't require Flutter's test host tooling (like the `flutter drive` command). 4. **Tooling and Libraries:** `integration_test` can work with existing test libraries and tooling, and supports features like setup and teardown methods, the `testWidgets` function, and Flutter's widget testing environment in general. 5. **Migration and Compatibility:** As of my last update, `integration_test` is being favored over `flutter_driver` by the Flutter team, and it's likely that the latter will eventually be deprecated. The team has also provided a migration guide for moving `flutter_driver` tests to `integration_test`. 6. **Performance Profiling:** `flutter_driver` supports performance profiling of the app while running tests. As of my knowledge cutoff in September 2021, `integration_test` does not support this, although this may change in the future. Overall, it's recommended to use `integration_test` for new projects, and consider migrating existing `flutter_driver` tests to `integration_test` if feasible. This is because `integration_test` simplifies the process of writing integration tests, and aligns more closely with other types of Flutter testing. However, if your project relies heavily on performance profiling during test runs, you may want to stick with `flutter_driver` until such functionality is available in `integration_test`.
hey, I am getting this error every time I run command for testing. { Could not find a file named "pubspec.yaml" in "/home/paras/.pub-cache/hosted/pub.dartlang.org/_fe_analyzer_shared-12.0.0".} Pls help me out. the path is correct that's confirmed, getting the same error on all integration test repo
so states_rebuilder added global functional injection, navigation support, dialog and snackbar features, how about a video series like the one you did with GetX? Seeing that the two are kinda of aiming for the same thing, I wonder which is better.
Thomas Mabika I've been planning on taking a look at that. But also I want to check out the get_cli and get_server and then Riverpod too. There's so much 😅
@@tadaspetra I say we start with states_rebuilder first, do 5 or so videos, then get_cli and server.... then if you really must, maybe Riverpod. What do ya think?
Thomas Mabika I appreciate that advise but I already got the other ones mostly planned out. And I still have a lot to learn and remember about states_rebuilder so that one will have to wait a bit. But I appreciate it 😊
@@tadaspetra in that case, I guess I'll just have to unsubscribe from the channel. Good luck. lol, just kidding, whatever decision you make mate, I'm just here for the content.
Alejandro Sánchez Durán not really. Reach of them have their own purpose. For unit testing you can check all the error cases for each specific function, and same thing for widget tests. There are also a lot deeper you can go into the different types of testing and they each serve their own purpose. BUT I think if you were to only do one type of testing, I think integration testing covers the most parts with fewer lines of test code.
