4. History of Testing
■ 1878 - Thomas Alva Edison uses the
first time the word „bug“
■ 1961 - Computer Programming
Fundamentals
– Gerald Weinberg & Herbert Leeds
■ 2009 - The Test Automation Pyramid
10. Demo
■ You should see now:
– Running Calculator Application
– All tests inside of the Repository are passing
– Code Coverage Gutter –VSCode Extension
UnitTest DemoVideo:
https://youtu.be/pEZXtktBuSo
11. Good to know in UnitTesting
■ Test should be complelty independent
– Try to run them randomly with
ShuffelingTesting
■ You can shard your tests
15. Demo
■ You should see now:
– MockCalculationService with Mockito
– Explanation of the differentTests
– SnapshotTest
WidgetTest DemoVideo:
https://youtu.be/u8toWolo4BE
17. IntegrationTesting
■ Flutter Driver Extension
■ New Folders and Files
■ Automated Execution test on real devices
■ Performance Profiling possible
18. Step I
Add dependency to
pubspec.yaml
Get started with Flutter IntegrationTest
Step II
CreateTest_driver Folder and
add two files.
Step III
Enable the Flutter Driver
Extension and runstartup your
application
19. Demo
■ You should see now:
– Test Driver Folder
– Calculator file that creates the application
– setUpAll / tearDown
– RealTestrun on a Simulator
UnitTest DemoVideo:
https://youtu.be/73leAh7sTxw
20. KeyTakeAways
■ IntegrationTests are quite heavy and run the whole app
■ Slow compared toWidget and UnitTests
■ E2ETesting with ease
■ PerformanceTesting
■ Mobile & Web Support (with Driver Extension)
21. Code Quality
■ Keep theTesting pyramid in mind
■ Flutter has a lot of tools to keep the quality high we just have to use
them
■ SellTesting
– SonarQube
– Test Coverage
– Quality Gates