Testing Basics

Transcript

1. DOES IT WORK THE BASICS Seth Clark - @setheclark
2. HOW DO YOU CONFIRM THIS CODE WORKS? THE PROBLEM
3. TESTING SOLUTION
4. TYPES OF TESTING Unit
5. UNIT TESTING ▸ Tests that verify that a specific (small) section of code operates as expected. ▸ Often performed on individual methods.
6. BENEFITS OF UNIT TESTING ▸ Easily cover all combinations of inputs and outputs ▸ Can Should be automated ▸ Quick to create ▸ Refactor protection ▸ Documentation PITFALLS OF UNIT TESTING ▸ Testing too much ▸ Designing code that can be unit tested.
7. TYPES OF TESTING Unit Integration
8. INTEGRATION TESTING ▸ Tests that verify that multiple units work together properly
9. BENEFITS OF INTEGRATION TESTING ▸ Covers most use-cases of a set of functionality ▸ Can be automated PITFALLS OF INTEGRATION TESTING ▸ Testing too much ▸ Designing code that can be integration tested.
10. TYPES OF TESTING Unit Integration System
11. SYSTEM TESTING ▸ Tests that verifies paths through an entire system work as expected.
12. BENEFITS OF SYSTEM TESTING ▸ Can be used to verify more complex real customer use- cases PITFALLS OF SYSTEM TESTING ▸ Difficult to write
13. TYPES OF TESTING Unit Integration System Manual
14. MANUAL TESTING ▸ Tests that are manually executed. ▸ Typically script based.
15. BENEFITS OF MANUAL TESTING ▸ Can cover tests that require interactions with entities outside of your system. PITFALLS OF MANUAL TESTING
16. UNIT TESTING IN JAVA apply plugin: 'java' dependencies { testCompile "junit:junit:4.12" }
17. JUNIT - TEST CLASS STRUCTURE @BeforeClass public static void setupClass() {} @Before public void setup() {} @Test public void testMethod1() {} @Test public void testMethod2() {} @After public void tearDown() {} @AfterClass public static void tearDownClass() {}
18. JUNIT - ASSERTIONS assertNotNull(new Object()); assertNull(null); assertEquals("String", "String"); assertFalse(false); assertTrue(true); assertThat(Arrays.asList(1, 2, 3), hasItems(2, 3)); assertThat("JUnit", both(containsString("J")).and(containsString("t")));
19. JUNIT - RUNNERS / SUITES @RunWith(Junit4.class) public class Tests { @RunWith(Suite.class) @Suite.SuiteClasses({ LoginTests1.class, LoginTests2.class, LoginTests3.class }) public class LoginTestSuite {}
20. JUNIT - RULES @Rule ExpectedException expectedException = ExpectedException.none(); @Test public void throwNPE() { expectedException.expect( NullPointerException.class); throw new NullPointerException(); } @Rule TestRule timeout = Timeout.seconds(1); @Test public void nextEndingTest() { while (true) {} }
21. TIPS //Use AssertJ or some other assertions library assertThat(new Object()).isNotNull(); assertThat(true).isTrue(); assertThat(Arrays.asList(1, 2, 3)) .hasSize(3) .contains(2, 3) .doesNotContain(4);
22. TIPS ▸ Keep your tests organized ▸ Never* ignore failing tests ▸ But if you do use @Ignore instead of commenting out the test ▸ Don’t prefix test methods with ‘test’ ▸ Standardize test method names ▸ Test expectations — not implementations