This document discusses QA challenges and best practices for testing SaaS applications. It provides an overview of SaaS and common challenges like frequent releases, client configurations, and security. It also outlines the typical components of SaaS testing including product testing, integration testing, data testing, security testing, and more. An example is given of the SaaS testing at SelectMinds which has two products, 54 clients, and uses both manual and automated testing across QA, staging and production environments. Best practices outlined include understanding the QA environment, scope, product and client ecosystem as well as using proper SaaS testing tools.

1. SaaS Testing

2. Topics
 SaaS
 QA Challenges
 QA Components
 SaaS @ SelectMinds
 QA Best Practices
 Q&A

3. SaaS
What is SaaS and Why SaaS?

4. Challenges
 Frequent Releases
 Client Configurations
 Client Specific Enhancements
 Security ( Role based access)
 Multi Platform
 Localization

5. Components
Product
Testing
Config
Testing
Speed
Testing
Test
Automation
Platform
Testing
Reliability
Testing
Integration
Testing
Data
Testing
Security
Testing

6. SaaS @ SelectMinds
 Startup
 Two Products
 Web & Mobile
 54 Clients
 Localization
 Frequent Releases

7. QA @ SelectMinds
Testing Type Environment Method Tools
Product Testing QA -Manual
- Automated
-Webdriver
-Saucelabs
Integration Testing QA - Automated - Webdriver
Mobile Testing QA /Staging -Manual
-Automated
-Handsets
-Perfecto mobile
Client Configuration Testing Staging Automated - Webdriver
Notifications Testing Staging Automated - EmailonAcid
Data Testing Staging Manual/SelfS
erve
Performance Testing Staging/QA Automated -Keynote
-New Relic
-Jmeter
-Yslow
Security Testing Staging Automated -Paros
- Third Party
Service

8. Best Practices
 QA Environment
 Understanding Scope
 Understanding the Product
 Understanding the Client Ecosystem
 Understanding and Using proper SaaS tools

9. Thanks!!!
Author: Ashok Mohanty
Email: amohanty.email@gmail.com
Twitter: la_test