Runtime Snippets is dedicated to deliver fast-paced coding content. We believe that education should be accessible to all, especially coding/programming related education.
Great video again! Would you mind further explaining why loops in tests are a bad idea? Following your other video on TDD, I came up with the following test: ```dart test("return 'Fizz' for multiples of 3", () { // arrange const inputs = [3, 6, 9, 12, 33, 66, 99]; // act for (int input in inputs) { final result = solver.execute(input); // assert expect(result, 'Fizz'); } }); ``` Should I divide it into multiple tests for each input? Wouldn't that be a lot more verbose? What is the correct way of thoroughly testing a functionality? Thanks in advance, you got a new subscriber!
1."Why are loops a bad idea in unit tests?" Because 1. loops go against readability and conciseness. 2. The flutter test suite will only give you one output per unit test. So let's say, if your unit test had 7 inputs and one of them was wrong, the entire test will fail. Which is not very descriptive, and doesn't provide you with the right feedback. We also won't be able to know on which iteration the expect method failed. We will have to debug this ourselves. 2. "Should I divide it into multiple tests for each input?" Absolutely! 3. "Wouldn't that be a lot more verbose?" Remember the rule from the TDD video: "Write specific test cases that make your code generic" Meaning: The more specific test cases you have, the more general your code will become in handling different inputs. So it doesn't matter the number of tests you have. One input = One output, and there should be a single test case for that. 4. "What is the correct way of thoroughly testing a functionality?" To thoroughly test a feature, you should identify different edge cases that will break the feature, and then test your code through those inputs. For example, in your method, maybe a multiple of 5 or a multiple of both 3 & 5, might break your feature, so I would test your code with those inputs as well. But be cautious, don't write test cases that keep on testing the same behavior. For example, writing a test case for 3, then 6, then 9, then 12 will keep testing the same behavior of the feature. Once a behavior has been verified, go for different inputs that will test some other part of the method, like 5 or maybe 15. Have any other questions? I would love to answer :)
error Error (Xcode): /Users/programmer/.pub-cache/hosted/pub.dev/persistent_bottom_nav_bar-5.0.2/lib/neumorphic_package_by_serge_software/neumorphic_card.dart:57:57: Error: The getter 'backgroundColor' isn't defined for the class 'ThemeData'. can you help me??
Thanks for the helpful suggestions! For the video zoom, yes, we are working on it. And for the code repo, if we give it out right now, then there is no point in coding along or following it. We will be giving it out once this tutorial is complete!
Thanks for a great video! I find that my tests work when I run them locally, but when I try to get my app approved in the Google Play Console, I can see from the short test videos that their robot can't find my fields for email and password. Have you experienced the same thing?
This requires a bit of debugging. For example, which device is the test emulated on? Run the tests on that device locally inside your flutter project and see if it gives the same error. Mostly if the device height is too small, or the content is overflowing, the robot won’t be able to detect those fields. These integration tests are different from the ones that Google runs. But the idea for debugging is the same. Hope it helps!
As a developer, I've faced challenges with theming in projects that have strong architectural support. However, this tutorial significantly aided me in building an app with well-structured theming. Thanks🥰
What if i have 2 files to execute after login? Can i do simply in one main method by calling the file names and without uninstalling the app after login?
as I understand, you have two files with integration tests, you can both by running "flutter test integration_test" and it will run all the integration tests that are inside the integration_test directory
Simple and to the point demonstration without any time waste, simple awesome. Would love to know if there is any way to achieve native UI communication like allowing notification/location permissions or connect to a WiFi network etc.
Sir.... I installed flutter & java sdk 11 & I'm using android studio emulator.... I entered the "flutter run" command.... then showed "gradle task assebling....". This output showed big time & some times showing error messages (ex: java error 41). Please help me....
Hi there, make sure you follow all the steps correctly from docs.flutter.dev/get-started/install and do the correct settings according to your operating system.
@@vishwa_randunu Please follow along to these videos for proper installation: For windows: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-Z2ugnpCQuyw.html For mac: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-hL7pkX1Pfko.html
