Sela

Test Automation for decision makers: Getting the most out of test automation

Description
Many laymen believe that starting to use test automation in a software project requires only to learn the relevant tool, and voila! You have test automation. Unfortunately, building a successful and useful test automation, with a real ROI, is much more complicated. Most people eventually learn about the pitfalls only the hard way… This course, designed primarily for decision makers, will give you an overview on the topic of test automation in order to help you lead a successful test automation project that will improve the entire application development lifecycle and its quality, and save your organization precious time and money!
Intended audience
This course is targeted primarily at decision makers in software development projects (mainly dev and QA managers), who either haven’t started with test automation yet, or have started but feel that it doesn’t provide the value they’d expected. In addition it can be useful for testers thinking about starting to use test automation and for anyone who is interested to learn more about test automation.

Topics

Functional tests
Unit tests and integration tests
Performance tests
Load and stress tests
Reliability
Maintainability
Diagnosing failures
Adopting manual tests to automation
Shortcomings of test automation
Enabling agility and rapid releases
Enable refactoring to improve inner quality and long-term maintainability of the software product
Continuous Improvement
Promote manual testers to become automation developers
Mixing manual testers and few automation developers (the “Building Blocks” pattern/KDT)
Dedicated automation team
Automation developers spread across development teams
A developer centric approach
The connection between the application’s architecture and the tests reliability
Designing the test automation to fit the application architecture
Deciding which components of the application to test for best ROI
Increasing reliability using isolation techniques
When to run the tests?
Handling bugs found by automation (important!)
When to write the tests?
Conway’s law
Layered architecture/organization vs a feature based architecture/organization
Self-organizing teams
Collaboration vs. blame culture
Tools for UI Automation: Selenium, Coded UI, Ranorex, UFT/LeanFT
Tools for Rest API: SoapUI, Rest Assured, hand-written
BDD style tools: SpecFlow/Cucamber, Robot Framework
ALM Tools: TFS/MTM, Jenkins
Load testing: VS Load Testing, JMeter

רוצה לדבר עם יועץ?

האם אתה בטוח שאתה רוצה לסגור את הטופס ולאבד את כל השינויים?