Software Testing Workshop 2014 Introduction

Transcription

1 Software Testing Workshop 2014 Introduction May 3 rd FAST, Islamabad.

2 About Us Majd Uddin 15+ years of experience with a decade in software testing Promoting software quality: M.Sc. (CS) from PUCIT, Lahore. B.E. (Mech) from UET, Taxila. Other interests include hiking, reading and blogging.

3 About Us Sohail Sarwar 5+ years of experience in Software Industry NUST-SEECS and Kraysis-Soft Lahore NUST-SEECS and DTS Japan NetsolAce Inc. Associate Software Quality Analysis Bentley Systems Pakistan ( Software Quality Analyst (Platform Technologies) National Engineering and Scientific Commission (NESCOM) Assistant Manager (Software Engineering) M.S.(IT)- Specialization in Software Engineering from SEECS,NUST PhD (CS) Iqra University Islamabad [In Progress]

4 ABOUT YOU

5 Today s mission

6 Breaking down the Mission Exploring systems Asking Questions Knowledge Tester Coding tests Designing tests

7 Photo from HubSpot free image library Is this a Quality phone?

8 Support the team (Agile) Testing Quadrants Automated & Manual Functional Tests Examples Story Tests Prototypes Simulations Unit Tests Component Tests Business facing Q2 Q1 Exploratory Testing Scenarios Usability Testing UAT (User Acceptance Testing) Alpha/Beta Q3 Q4 Performance Tests Load Testing Security Testing ility Testing Manual Critique Product Automated Technology facing Tools From Agile Testing book by Lisa Crispin and Janet Gregory

9 Imaginary Software Client Programmer Tester

10 Asking Questions EXERCISE 1

11 END OF MODULE 1

12 Software Testing Workshop 2014 Designing Tests May 3 rd FAST, Islamabad.

13 Test Cases A Test Case or a Test is an Action performed on System Under Test (SUT) where we expect a Behavior and We can state if a Test Passed, Failed or needs discussion

14 Ideas for Tests (Heuristics) S is for Structure F is for Function D is for Data P is for Platform O is for Operations T is for Time H is for History I is for Image C is for Comparable Products C is for Claims U is for User Needs P is for Product P is for Purpose S is for Statutes SFDPOT by James Back, HICCUPS by Michael Bolton

15 Documenting Test Cases Test Cases Repository Feature Test Plan in form of sheets/docs Mind Maps Check Lists

16 Just enough Documentation اہیں اتزہ یلھچم دایتسب ےہ

17 Designing Tests EXERCISE 2

18 END OF MODULE 2

19 Software Testing Workshop 2014 Coding Tests May 3 rd FAST, Islamabad.

20 The objectives 1 Software Test Automation? 2 Automation Tools 3 Automation Implications

21 Software Test Automation Software Test Automation is to control the execution of tests by comparing actual and expected outcomes. Tester writes scripts and uses another software to test the software Automated tests once developed, can be run repeatedly

22 Rationale for Test Automation Manual execution of test plans for regression testing is laborious and time consuming. Test automation is handy for products with long maintenance life It can test the application from performance, load and stress point of view. Saves time and money compared to error-prone manual testing. Improvises test accuracy, coverage and productivity.

23 How we can automate? What to Automate??? Choosing an automation tool Creating a testing infrastructure for automation Designing of test cases Development of scripts Execution of Scripts Analysis of Results Sharing the results with team Maintenance of Scripts

24 Automation Tools Different tools with respective features are there: API Testing Nunit, Junit GoogleTest, Visual Studio Test Suite GUI Testing SilkTest, TestComplete WinRunner Performance Testing LoadRunner, WebLoad

25 NUnit NUnit is a unit testing framework for the.net Language NUnit promotes the idea of "first testing then coding NUnit is an open source framework which is used for writing & running tests Provides annotations, assertions and test runners

26 Environment for NUnit Microsoft Visual Studio 2010.NET 4.0 NUnit 2.6.0

27 xunit Design Code to Test Test Code Test Runner

28 Unit Tests in NUnit Unit Test is code that ensures another part of code (method) works as expected. Unit tests can be written using a test framework such as Nunit. Unit test can be characterized with a known input and an expected output. Input corresponds to pre-condition and expected output corresponds to post-condition. Each requirement may have two test cases: positive and negative ones.

29 Writing Tests using NUnit Let s write our first test..

30 Automating Adder Application Application: Adder application which takes two 2-digit no.s and displays the sum.? 2? 3 5

31 Adder Application Test Scenarios -I

32 Adder Application Test Scenarios -II

33 NUnit Features Assertions Equal, Null, True [with respective vice versa] Annotations of Nunit [Test] [Test Fixture] [SetUp] - before each test method is called [Teardown] - after each test method is run [TestFixtureSetUp] - performed once prior to executing all tests in fixture [TestFixtureTearDown] - performed once after all tests are completed [ExpectedException] [Ignore()]

34 Parameterized Tests Help in running the same tests over and over again using different values Nunit offers the same feature via [TestCase(12,3,4)] [TestCase(12,2,6)] [TestCase(12,4,3)] public void DivideTest(int n, int d, int q) { Assert.AreEqual( q, n / d ); }

35 Generating Test Documentation [TestFixture, Description("Fixture description")] public class SomeTests { [Test, Description("Test description here")] public void DocTest() { /*... */ } }

36 A Step Ahead---- DAO design Pattern Business Logic Layer Data Transfer Objects Data Access Objects DB Utility

37 Do and Don t of Test Automation Smoke Testing Run with every build to make go/no-go decision on deeper testing. Regression Testing Assures that a change, bug fixes or new functionality, did not introduce new bugs Data Driven Testing Testing the operations with their related data sets in a framework Exception or Negative Testing Forcing error conditions in the system. Functional Testing Testing that operations perform as expected for relatively stable application Testing on different Operating Systems/Environments Repetitive tasks

38 Do and Don t of Test Automation Exploratory testing Usability testing Documentation Testing Graphics Testing For Features which are under changes/unstable

39 Software Testing, A research Perspective Automated Tools for Reliability calculation of Critical system Test Case Generation for Regression testing Test Case prioritization technique Software testing in offshore culture with agile models Testing of semantic Web applications.

40 Questions Questions

41 References.. Automated Testing Best Practices Open Source Testing Tools in C# Automation Concepts Google C++ Testing Framework 'Testing Computer Software' book by Cem Kaner, Jack Falk and Hung Q. Nguyen.

42 END OF MODULE 3