This document provides an overview of quality testing for developers, including different types of tests like unit tests, integration tests, and platform tests. It discusses testing at the component, product, and platform levels. It also covers test automation technologies, frameworks like TestNG for test execution and reporting, and techniques like page objects for UI testing. The key goals of testing are to verify correct integration and behavior across components and products, and to cover real-world use cases, performance, security and other quality attributes.

1. Quality For Developers

2. What do you think ??????

3. Testing Good Bad And Ugly

4. Understanding - Cost of test Wrong way

5. Understanding - Cost of test Right way

6. "Agile Development" is an umbrella term for several
iterative and incremental software development
methodologies

7. Basic Understanding - Unit Test
● Focused on testing behavior of a
particular class, module or method.
● Smallest part of the application.
● Fast (less than 0.1 second per test)
● No external implementation
dependencies
(filesystem, database, web services, etc.). All
dependencies are faked for the test context.
● Can easily be parallelized, since each test is atomic

8. Basic Understanding - Integration Test
● Focused on verifying the integration
of one or more components together.
● May have external dependencies.
● A test that takes longer than a unit
Test should
Integration Tests - with in WSO2
● Executes on product pack created by build.
● Not depending on other product environments.
● Independent.
● Lightweight.
● Covers only scenarios related to features on individual product.

9. How tests really looks like
Platform - Platform Tests
Cross Platform Tests
Product - Integration Tests
Component
- Unit Tests
Component
- Unit Tests
Component
- Unit Tests
Component
- Unit Tests
Product - Integration Tests
Component
- Unit Tests
Component
- Unit Tests
Component
- Unit Tests
Component
- Unit Tests
Product - Integration Tests
Component
- Unit Tests
Component
- Unit Tests
Component
- Unit Tests
Component
- Unit Tests
Product - Integration Tests
Component
- Unit Tests
Component
- Unit Tests
Component
- Unit Tests
Component
- Unit Tests

10. ● Platform scenarios.
● Integration scenarios.
● UI scenarios.
● Real world use cases.
● Performance and Security scenarios.
● Patches provided.

12. Technologies for Automation
Test Framework Build Systems
Code Coverage
Extensibility Support
UI Automation

13. ●
●
●
○ Trigger out TestNg.
○ Control TestNG flow (Through Surefire TestNg Utils)
○ Generate reports. (Html, XML and emailable report)

14. Execution Started
@BeforeSuite
@BeforeTest
@AfterTest
@AfterSuite
Execution Closed
@BeforeClass
@BeforeGroups
@BeforeMethod
@AfterMethod
@AfterGroups
@AfterClass

15. ● Listeners are interfaces allows to modify TestNG's
behavior.
● Listeners are binned to a testNg execution.
● Listeners implement the interface org.testng.ITestListener
○ IExecutionListener
■ Triggers at start and end of any execution.
■ ISuiteListener.
○
■ Triggers at suite start and end.ITestListener
■ Triggers at Test start, Finish, Failure, Skip and partial failure.
● Reporters implement the interface org.testng.IReporter
○ Notified when all the suites have been run by TestNG.
○ The IReporter instance receives a summary of entire test run

16. ●
○ Offline instrumentation
○ On fly instrumentation
●
●
○ Code coverage
○ Class coverage
○ cyclomatic complexity

17. ● Reduces the amount of duplicated code.
● Encapsulate the internal state of a page into a single
page object.
● UI changes only affect to a single Page Object, not to
the actual test codes.
● Code reuse: Able to use the same page object in a
variety of tests cases.
Page Object
Class
Mapper.properties
Test Class

18. Questions?

19. Contact us !