460 likes | 468 Views
Learn about the importance of early developer testing and how to implement automated test driver frameworks. Discover how these frameworks can save your reputation and improve the efficiency of your testing process.
E N D
WARNING • These slides are not optimized for printing or exam preparation. These are for lecture delivery only. • These slides are made for PowerPoint 2010. They may not show up well on other PowerPoint versions. You can download PowerPoint 2010 viewer from here. • These slides contain a lot of animations. For optimal results, watch in slideshow mode.
How long will they take to catch all fish? Less than 1 hour Around 1 hour About 100 hours Forever [Extra] 100 fish If 100 people trying to catch 100 piranha fish. On average, one person can catch one fish within 1 hour
How long will they take to catch all fish? Less than 1 hour Around 1 hour About 100 hours Forever [Extra] 100 fish If 100 people trying to catch 100 piranha fish. On average, one person can catch one fish within 1 hour
How long will they take to catch all fish? Less than 1 hour Around 1 hour About 100 hours Forever [Extra] 100 fish If 100 people trying to catch 100 piranha fish. On average, one person can catch one fish within 1 hour
System testing SUT
System testing SUT
System testing SUT
[Extra] who wants maximum publicity Do you want maximum publicity for your mistakes?
[Extra] who wants maximum publicity Do you want maximum publicity for your mistakes?
Never too early to test: An Introduction to Early Developer Testing
MSLogic History UI MSLogic History UI Storage Unit testing Storage
MSLogic History UI MSLogic History UI Storage Unit testing Storage
Unit testing Test Driver SUT==MSLogic UI MSLogic History Stub Storage String item = msLogic.getItem(1); if(!item.equals(“Item1”) print(“Case 1 failed”); …
Unit testing Test Driver SUT==MSLogic UI MSLogic History Stub Storage String item = msLogic.getItem(1); if(!item.equals(“Item1”) print(“Case 1 failed”); …
String item = msLogic.getItem(1); if(!item.equals(“Item1”) print(“Case 1 failed”); … assertEquals(msLogic.getItem(1), “Item1”); JUnit Testing frameworks
Automated UI MSLogic History Storage A type of Unit testing Developer testing
SUT Test-Driven Development (TDD)
Write a failing test Write code to pass test Test-Driven Development (TDD)
CityConnectTest.java CityConnect.java
CityConnectTest.java CityConnect.java
CityConnectTest.java CityConnect.java Clementi true Novena true Eunos true Changi false Clementi, Eunos, 20 Eunos, Novena, 40 Write the java code for the above
CityConnectTest.java CityConnect.java
CityConnectTest.java CityConnect.java
CityConnectTest.java CityConnect.java
CityConnectTest.java CityConnect.java
CityConnectTest.java CityConnect.java
CityConnectTest.java CityConnect.java
CityConnectTest.java CityConnect.java
CityConnectTest.java CityConnect.java
CityConnectTest.java CityConnect.java
CityConnectTest.java CityConnect.java
CityConnectTest.java CityConnect.java
CityConnectTest.java CityConnect.java
CityConnectTest.java CityConnect.java
CityConnectTest.java CityConnect.java
CityConnectTest.java CityConnect.java
CityConnectTest.java CityConnect.java
CityConnectTest.java CityConnect.java
CityConnectTest.java Note: more test cases required. CityConnect.java Refactor as necessary.
Write a failing test Write code to pass test Test-Driven Development (TDD)
[Extra] who wants maximum publicity Do you want maximum publicity for your mistakes? When the system test fails...
It can save your reputation. Must do developer testing Can do in TDD fashion Only system testing? NO Use automated test driver frameworks