Foundation level testing Concepts,Non function testing ,Non-Functional testing ,Selenium Tool, What is Software Testing Software Testing is an activity in software development. It is an investigation performed against a software to provide information about the quality of the software to stakeholders. Software testing is associated with the two terms. Validation: Are we doing the right job? Verification: Are we doing the job right? Case study "Virtual Show Room" – VSR,water fall model,General Principles of Testing, The General V-Model Unit Testing Component Testing Integration Testing System Testing Acceptance Testing

1. TESTING
CONCEPTS
By:
Sangamesh Kumbar

2. Foundation level testing concepts
Non-Functional testing
Test Automation
Selenium Tool

3. What is Software Testing
 Software Testing is an activity in software development.
 It is an investigation performed against a software to provide information
about the quality of the software to stakeholders.
 Software testing is associated with the two terms.
Validation: Are we doing the right job?
Verification: Are we doing the job right?

4. Case study "Virtual Show Room" –
VSR shows possible models and
combinations of extra
equipment, and instantly
calculates the accurate
price of the configured car
Suitable
payment
Place the
order online
Appropriate
insurance
Configure their favorite model

5. The Fundamental Test Process

6. General Principles of Testing
 Principle 1: Testing shows the presence of defects, not their absence.
 Principle 2: Exhaustive testing is not possible.
 Principle 3: Testing activities should start as early as possible.
 Principle 4: Defects tend to cluster together.
 Principle 5: The pesticide paradox.
 Principle 6: Test is context dependent.
 Principle 7: Absence of error fallacy.

7. The General V-Model
Unit Testing
Component Testing
Integration Testing
System Testing
Acceptance Testing
Section II

8. Unit Testing
 In this testing we will test individual functionality of modules.
 We will test functions and it’s output.
 Done By Developer.
Admin Module
Functions Methods
Loop’s Statement’s
Example:

9. Component Testing
 Component testing is one of the testing technique in which the testing is
performed on each individual component separately without integrating with
other components.
1
2
3
4
5
Website

10. Integration Testing
 In integration Testing, individual software modules are integrated logically
and tested as a group. (Incremental and Big Bang Approach)
Top Down Approach Bottom Up Approach
Lower Modules Lower Modules
Higher ModulesHigher Modules

11. System Testing
 System Testing is the testing of a complete and fully integrated software product.
 Software is interfaced with other software/hardware systems.
 System Testing is actually a series of different tests whose sole purpose is to
exercise the full computer based system.

12. Acceptance Testing
 User acceptance is a type of testing performed by the Client to certify the system with respect
to the requirements that was agreed upon.
 This testing happens in the final phase of testing before moving the software application to
Market.

13. The General V-Model
Coding
Module Design
Software Design
System Analysis
Requirement
Gathering
Acceptance Test
System Test
Integration Test
Component Test
Verification Validation

14. 1 31
Above Below
320
Below Above
Lower Boundary Upper Boundary
1. 1
2. 2
3. 3
4. .
5. 31
1. 31
2. 32
3. 33
4. .
5. ..
Invalid Input Valid Input Invalid Input
1. 0
2. -1
3. -2
4. .
5. ..
OFF ON
Turn ON
Turn Off
Test Design Techniques of Black Box
 The method in which internal structure of the Product is not known to the
tester.
 4 important software testing techniques-
 Equivalence Class Partitioning
 Boundary Value Analysis (BVA)
 Decision Table based testing.
 State Transition

15. Test Design Techniques of White Box
 The method in which internal structure of the product is known to developer.
 2 important software testing techniques-
 Statement Coverage
 Branch Coverage

16.  Non-Functional testing
Compatibility testing
Performance testing
Security testing

17.  Functional testing
 Functional testing is also known as component testing.
 Component’s : test box, check list, drop down, radio button, links, etc..
 Is a type of software testing in which software is tested against
functional requirements or specifications with the intend to find a bug
or defect(s) if any.
 Functional testing (verifies, design) is different from System testing
(validates, system) .

18. Example: SRS document for Login
1. Login
1.1 username : should accept 8 – 22 character.
1.2 password : should accept 8 – 22 character, special characters are
allowed.
1.3 …
2. Forgot Password
2.1 …
2.2 …
3. … Login

19. Compatibility testing
 Compatibility Testing is a type of Software testing to check whether your software is capable of
running on different hardware, operating systems, network environments or Mobile devices.
 Types:
There are two types of version checking

20. Compatibility testing Example:
Gmail in Old version of Firefox Gmail in New version of Firefox

21. Performance testing
 Performance Testing is a type of testing to ensure software applications will perform well
under their expected workload.
 The focus of Performance Testing is.
 Speed - Determines whether the application responds quickly.
 Scalability - Determines maximum user load the software application can handle.
 Stability - Determines if the application is stable under varying loads

22. Security testing
 Security Testing is a variant of Software Testing which ensures, that system
and applications in an organization, are free from any loopholes that may
cause a big loss.
 Security testing of any system is about finding all possible loopholes and
weaknesses of the system which might result into a loss of information at the
hands of the employees or outsiders of the Organization.

23. Types of Security
testing

24.  Basic concepts of Test
Automation
Why Automation?
Automation process
Automation Tools
Types of software testing that can be automated

25. WHY AUTOMATION ?
 Manual testing of all work flows, all fields, all negative scenarios is time and cost
consuming.
 It is difficult to test for multilingual sites manually.

26. CONT.,
 Automation does not require human intervention.
 Automation increases speed of test execution and test coverage.

27. DISADVANTAGE
Its not easy
Automation Script
error
Complexity
Debugging

28. CAN EVERYTHING BE
AUTOMATED ??
There are cases when automating is not required or feasible.
 Application is changing in near future.
 Very tight deadline.

29. AUTOMATION PROCESS
Test tool selection
Define the scope of Automation
Planning, Design, and Development
Test Execution
Maintenance

30. Features HP QTP IBM RFT Selenium
License Required Required Open Source
Cost High High Free
Customer Supp. Yes Yes Yes: OSC
Coding Skills Low Low Very High
Environment
Supp.
Windows Windows Windows , Linux,
Mac
Automation Tools

31. TYPES OF SOFTWARE TESTING THAT
CAN BE AUTOMATED
1. Unit Testing
2. Integration Testing
3. Functional Testing
4. Regression Testing
5. Black Box Testing

32.  SELENIUM
What is Selenium
Why use selenium
Versions and suite of Tools.
How to set-up selenium
Hands-on!

33. WHAT IS SELENIUM
“Selenium is an open-source tool that can automate
almost any web browser “
 Selenium can only be used to test web applications.
 Selenium is fast and easy to use even with large set of data,
and has guaranteed accuracy.

34. WHY USE SELENIUM
Being open-source, selenium is available for free.
Selenium works good with any operating system.
Selenium lets you perform tests on any web browser.
Selenium supports for multiple programming languages.

35. VERSIONS AND SUITE OF
TOOLS
 Selenium RC
 Selenium IDE
 Selenium WebDriver

36. HOW TO SET-UP SELENIUM
JAVA
Eclipse
Selenium
https://www.seleniumhq.org/download/

37. TEST CASE EXAMPLE 1 :
 Search Some text in Bing search engine
1> 2
>

38. TEST CASE EXAMPLE 2 :
 Creating Facebook using selenium automation
1> 2
>