Downloaded 17 times
Uploaded byDharshana Kasun Warusavitharana
Automation for developers
The document discusses an automated testing framework for developers, emphasizing the importance of testing behavior through unit and integration tests while minimizing dependencies. It highlights features such as a lightweight execution engine, user-friendly configuration management, and support for multiple product management within a single test. Additionally, the framework supports various technologies and provides extensibility options for customization and reporting.
More Related Content
Similar to Automation for developers
Automation for developers
- 1.
- 2. ● We aresuper developers and we don't make mistakes. ● I never do changes to my code. ● I am the life time owner of my code. ● I am the only person who use each component I build. ● We have telepathic. ● My code runs on each platform ○ Its platform vendor’s responsibility to make platforms unique.
- 4. What do youthink ??????
- 5. Who write thecode ?? Who works with your code??
- 6. ● ● ● ● ●
- 7. “Quality is free,but only to those who are willing to pay heavily for it.” - Lister, Demarco: “Peopleware”
- 8. ● ● ● ● ● ●
- 9. Testing Good BadAnd Ugly
- 10. ● ● ● ● ● ●
- 11. ● ● ● ● ●
- 12. ● ● ● ●
- 13. ● ● ● ● ● ●
- 14. Understanding - Costof test Wrong way
- 15. Understanding - Costof test Right way
- 16. 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
- 17. 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.
- 18. ●● ○○○○○○○ ● M = E − N + 2P, where E = the number of edges of the graph. N = the number of nodes of the graph. P = the number of Connected Components ● fi
- 19.
- 20. Jacoco /EclEmma coveragereport Emma coverage report
- 21. ● Platform scenarios. ● Integration scenarios. ● UI scenarios. ● Real world use cases. ● Performance and Security scenarios. ● Patches provided.
- 22. How tests reallylooks like Platform - Platform Tests Product - Integration Tests Component Component - Unit Tests - Unit Tests Cross Platform Tests Component - Unit Tests Component - Unit Tests Product - Integration Tests Component Component - Unit Tests - Unit Tests Component - Unit Tests Component - Unit Tests Product - Integration Tests Component Component - Unit Tests - Unit Tests Component - Unit Tests Component - Unit Tests Product - Integration Tests Component Component - Unit Tests - Unit Tests Component - Unit Tests Component - Unit Tests
- 24. What got betterand bigger ● Lightweight test execution engine. ● More focus on platform wide scenarios. ● More user friendly configuration management. ● Ability to extend TestNG based listener implementation ○ Ability to plugin custom servers like Tomcat, CXF ,ActiveMQ, Apache FTP and more. ● Ability to come up with your automation story.
- 25. Organization Test AutomationFramework modules Engine Extensions Admin Service API Core - Utilities Automation Test Core Servers External Tools Extensibility Modules Configuration
- 26. Overall Architecture SupportModules Test Automation Framework Test Build platform -Maven Test Trigger- Surefire Testing Framework - TestNg Test Suite Configuration platform Automation.xml Extensible module handling Context Management Coverage Instrumentation.txt Pluggable Extensions TestNg Listener Extension Modules Server Management Tenant Management Test Tooling Extensions Engine TestNg Listener Extensions Configuration Management Admin Service API Reusable core utils filter.txt Test Configurations TestNg.xml TeTsetNstgN.xgm.xlml
- 27. Flexibilities Provided ●Manage several products inside single test. ● Manage users in several product domains. ● Deployment of artifacts for different products under different users. ● Configured admin service clients as test oriented API. ● Retrieving test environment configurations easily. ● Running same test in both local and Stratos environments. ● Reporting TestNg and surefire reports for all your tests. ● Tooling support of Selenium and Jmeter.
- 28. Technologies for Automation Test Framework Build Systems Code Coverage Extensibility Support UI Automation
- 29. ● Like JUnitbut not JUnit ● Annotation based Architecture ● Test Grouping ● Extensibility features ○ Listeners ○ Bean Shell ○ Annotation Transformers ● Easiness of managing Test cases. ● Failed test execution (Straight and easy)
- 30. ● ● ● ○ Trigger out TestNg. ○ Control TestNG flow (Through Surefire TestNg Utils) ○ Generate reports. (HTML, XML and emailable report)
- 31. Execution Started @BeforeSuite @BeforeTest @BeforeClass @AfterTest @AfterSuite Execution Closed @BeforeGroups @BeforeMethod @AfterMethod @AfterGroups @AfterClass
- 32. ● Listeners areinterfaces 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. ○ 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
- 33. ● ○ Offlineinstrumentation ○ On fly instrumentation ● ● ○ LOC coverage ○ Class coverage ○ cyclomatic complexity
- 34. ● ● Automation.xml Common Extensions Test Suite Test Suite Extensions Test Suite Utilities Test classes Automation Framework Engine
- 35. ● ● ● ●
- 36. ● Includes allutility classes that can play supportive role inside a test. ○ Ex :- ■ Axis2 client. ■ Wire message monitor. ■ Custom server startup scenarios (Axis2, Tomcat, ActiveMQ). ■ Concurrency test scenarios. ■ Rest Clients. ● Provides common methodology for all development teams and Automation team to maintain a set of supportive classes without changing the Core.
- 37.
- 38.