Oracle OpenWorld saw a fantastic session on testing on the 26th which provided an overview of how quality assurance teams test Oracle E-Business Suite. The session covered the main areas to consider during functional testing, approaches for new feature and regression testing, how to reduce the test script generation and execution time, metrics to showcase the ROI of a testing investment, leveraging automation for testing, and more!
Businesses are transforming at a rapid pace now. It’s not just about applications anymore. It’s also about mobile, cloud, analytics, social, and the internet of things which has led to quick go live turnaround, faster adoption rate of new technology, increase in complexity and usage pattern. The new additions have their own challenges as well. Apart from the traditional functional, UI, performance, security, transition, installation, usability, and accessibility testing, the things to consider and test separately are OS, OS versions, devices, device models, networks.
The new and evolved testing requires balancing testing with quality, analyzing and freezing requirements, designing documentation, building test automation and manual testing strategies. Some of the challenges organizations face in the process are:
- No common centralized repository
- Loss of testing artifacts due to change
- Difficulty in tracking progress
- Gaps in test plans
- No traceability
- Inconsistency in structure
- Improper severity and duplicate defects
- Lack of artifacts
Automation eliminates the need for module specific testers. Robust automation scripts translates into less script maintenance , and establishing automation framework and creation of test scenarios saves times and builds consistency. So the question is who performs the automation, what should be automated, and when it should be done.
The users should consider automation of high priority and most repeatable flows when it’s high priority and the application is stable.
To achieve that, one needs organization alignment on testing and some of the best practices are:
- Formulating test scenarios
- Prioritizing based on large usage pattern
- Optimizing test scenariosç
- Creating test data volume and variety
- Testing workshops for group and role based testing
Learn more about Testing here.