Static & Dynamic Testing using Tools. Created by Kudakwashe K. Chambwe

Size: px

Start display at page:

Download "Static & Dynamic Testing using Tools. Created by Kudakwashe K. Chambwe"

Blake Reeves
6 years ago
Views:

1 Testing Tools Static & Dynamic Testing using Tools Created by Kudakwashe K. Chambwe

2 Motivation We will not mention any commercial tools in this chapter, [ ] this book would date very quickly. Tool support for testing, Chapter 6. (Black m ) Goal: Provide you with the fundamental understanding of various testing tools used in the industry.

3 Introduction

4 Introduction Where does it all t in?

5 Agenda 1. Why do we need Testing tools? 2. Static Testing What? Examples Why? Why not? How (Demo) 3. Dynamic Testing What? Examples Why? Why not? How (Demo) 4. Who uses the tools and when?

6 Why do we need Testing Tools? During the Software Development Process, testing can be Expensive 2. Time-consuming 3. Resource-consuming

7 We need tools because they're... i. Automatic Increase e ciency and save time when performing repetitive tasks like regression testing, or to support tasks like planning, design, reporting and monitoring. ii. Scalable Some activities require a signi cant amount of resources. (e.g. static analysis) iii. Required Some activities are impossible to do manually like large-scale performance testing (e.g. client-server / e-commerce apps)

8 Static Testing Static Code Analysis

9 What? defect? "aka. "bug" or "fault". A aw in a component / system that can cause the component / system fail to perform its required execution (e.g. incorrect statement)" (Black m ) static code analysis? "Analyzing code without actually executing it." (Black m ) Goal: Find defects, whether or not they might cause failure.

10 * =? * =? answer? positive/negative?

11 Examples Static analysis tools can generally be divided into 3 (three) categories: i. Coding standards Naming conventions, layout speci cations (indention) Examples: Linters (ESlint, JSLint), Checkstyle ii. Metric computation Structural attributes of the code (i.e. frequency, nesting, complexity etc.) Examples: SonarQube/SonarCloud, Veracode, Coverity iii. Code structure (i.) Control ow structure (unreachable code, cyclomatic complexity) (ii.) Data ow structure (unused, unde ned / unreachable variables), (iii.) Data structure (data organization) Examples: SonarQube/SonarCloud

12 Why? Early detection! nd defects early before test execution. see. principle #3 Early warning! be warned about suspicious aspects of the code (e.g. security), design, requirements. Cost reduction! detecting defects early allows for reduction of cost in relation to bug- xing. Improve code quality! help to enforce coding standards and analyze the structure and dependencies. Better understanding! help developers understand the structure of the code.

13 Why not? Are they always precise?

14 Why not? outcome #1. False-negative "aka. "False-pass result". Fails to identify the presence of a defect that is actually present." (Black m ) outcome #2. False-positive "aka. "False-fail result". A defect is reported but actually doesn't exist in the test object." (Black m )

How? SonarCube Open Source platform (2007), Sonarsource. Source code Quality Management tool built on "SonarQube". Supports 20+ programming languages (C/C++, Javascript, Java, C#, PHP, etc.

15 How? SonarCube Open Source platform (2007), Sonarsource. Source code Quality Management tool built on "SonarQube". Supports 20+ programming languages (C/C++, Javascript, Java, C#, PHP, etc. ) Features Doesn't just show what's wrong, but how to x it! Wide range of metrics (bugs, coding rules, duplication, complexity, architecture etc.) Provides quality indicators and visual scales to motivate improvement Shows progress through quality metrics

16 Demonstration SonarCloud

17 Dynamic Testing Unit Testing & System Testing

18 What? de nition? "Technique used to test software by executing it." (Black m ) Can be divided into 3 (three) subcategories 1. Speci cation-based (BB) 2. Structure-based (WB) 3. Experience-based

19 What? i. Test execution tool? "aka. "test-running tool".mostly capture/playback tools. Driven by scripting languages to automate actions for di erent values (i.e. input) and depending on di erent outcome(s) (i.e. output)" (Black m ) ii. Unit test framework tool? "A tool that provides an environment for unit/component testing in which a component can be tested in isolation using stubs and/or drivers. " (Black m )

20 Examples i. Unit testing aka. "Component / Module testing". Testing at the most granular level. E.g. functions, classes, procedures, interfaces etc. Examples: JUnit, Jest), PHPUnit, Jasmine, Mocha, PyUnit function multiplier (a, b){ return a*b; } test("multiply two integers", () => { expect(multiplier(2, 0)).toBe(0); });

21 Examples ii. Integration testing Testing the integration / interface between components, interactions to di erent parts of the system. E.g. OS, le system, HW, system-to-system etc. Examples: JUnit, Jest), PHPUnit, Jasmine, Mocha, PyUnit iii. System testing Testing the behaviour of the whole system / product. Investigate the functional and non-functional requirements of the testing. During system testing we might do UI testing, Browser testing, E2E testing, Functional testing, Load, Stress, Security etc. Examples: Ranorex, Selenium IDE), TestingWhiz

22 Why? Unit Testing Early detection! issues are found early by developers, when testing their own code. Easier to solve issues too. Easy maintenance & refactoring! by making code less interdependent, chances of impact to other code is limited. Cost e ective! nding bugs early helps reduce the cost of bug xing.

23 Why? System Testing Improved regression testing! repetitive work like regression testing can be more done in a more resource / time e ective manner. Can even cut costs too. Less subjective bias! tool calculations / metrics, provide a objective assesment of our code, making it also more realiable and consistent.

24 Why not? outcome #1. probe e ect The e ect on the system / compoennt by the measurement tool its being measured. (Black m ) E.g. performance may be worse when performance testing tools are being used.

25 How? Jest Javascript Unit Testing Framework tool, developed by Facebook. Recommended for React apps, but can be easily integrated into other apps / frameworks. Well supported and documented. Features Easy setup helps to get started without much con guration. aka. "zero-con guration". Snapshot testing ensures that your app's UI doesn't change unexpectedly between releases. Feature-rich library with a wide API.

How? Selenium IDE Capture & Playback tool for Browser/UI/E2E/Functional testing, Selenium HQ. Open source Firefox add-on that is also a comprehensive test automation tool.

26 How? Selenium IDE Capture & Playback tool for Browser/UI/E2E/Functional testing, Selenium HQ. Open source Firefox add-on that is also a comprehensive test automation tool. Features Record and playback function. Allows for creating and modifying test scripts and recording, editing and debugging tests. Record in Selenese, a test scripting language for Selenium for performing actions within a browser (i.e. clicking, selecting etc.).

27 Demonstration Jest Selenium IDE

28 Who uses thes tools and when?

29 The end.

Test Automation. Fundamentals. Mikó Szilárd

Test Automation. Fundamentals. Mikó Szilárd Test Automation Fundamentals Mikó Szilárd 2016 EPAM 2 Blue-chip clients rely on EPAM 3 SCHEDULE 9.12 Intro 9.19 Unit testing 1 9.26 Unit testing 2 10.03 Continuous integration 1 10.10 Continuous integration