This document summarizes the evolution of software testing from waterfall to agile methodologies. It discusses how automation is key to testing and provides examples of popular testing frameworks for different technologies. It also addresses finding the right balance between time and quality in testing. The document recommends starting with automating the most used user flows and critical paths. It stresses the importance of constant learning and sharing knowledge with the community.

1. Software Testing
Evolution of
Chuan Chuan Law
@ChuanCLaw

2. AGENDA
1 Testing & Software Engineering
2 Automation
3 Time and Quality
4 Where to go from here

3. Testing and Software
Engineering
PART ONE

4. Waterfall to Agile

5. KEEP CALM
AND LOVE
SOFTWARE
ENGINEERING

6. Bug Catching at Every Phase

7. Experience: Agile over Waterfall
• Quality: better quality
• Time: delivery on time
• Cost: less costly bug fixing
• Stakeholder: correct product to stakeholder
• Staff: less pressure on tester

8. Getting Rid of Documentation

9. Getting Rid of Documentation

10. Automation is Key
PART TWO

11. No Technology is Perfect without a
Testing Framework

12. Examples
• Web applications: Selenium
• Mobile: Calabash, Appium, Robotium
• .NET: Nunit, Xunit
• Java: JUnit
• AngularJS: Protractor

13. Choosing the Right Tool

14. Choosing the Right Tool
• Most popular used
• Community support
• Open source vs Commercial
• Skills
• Custom built
Eg: WebClient class (System.Net) for API & web services

15. Where to Start the Transition?
• BDD <= Test case, test plan
eg: SpecFlow
• Simple web driver commands
eg: driver.Navigate().GoToUrl()

16. Example: Where to Start?
More complex logic manipulation
eg: IWebElement t = driver.FindElement(By.XPath("//td[@id='content']/div[2]/b"));
_jobmsg = t.Text;
int i = 0;
while (_jobmsg[i].Equals('#') == false)
{i++;}
i = i + 2;
int x = 0;
while (i < _jobmsg.Length)
{
_jobmsg.CopyTo(i, _jobno, x, 1);
i++;
x++;
}

17. Example: Where to Start?
Framework level
eg: Helpers, reusable code
Battling with Selenium drawback
eg: Pages with lots of AJAX calls

18. Test = User + Design

19. Example: User + Design
Can pick up more edge case/boundary
testing
Eg: Enter 100 chars into a DB field varchar(50)
Helps understanding the effect of changes
Eg: Changing a CSS file that is shared across multiple locations

20. TIME vs QUALITY
PART 3

21. Time vs Quality
Bugs

22. Time vs Quality
Critical Path

23. Time vs Quality
Informed Data

24. Example
Situation:
 No automation at
all
 Complex product
 Time pressure
Solution:
 Gather top 20 (90% of usage) most
visited pages
 Analyse the user flow
 Automate the scenario

25. Where to Go from
Here?
Part 4

26. Staying Alive

27. Constant Learning

28. Learning does not always cost $$

29. Different Channels
Online conferences
eg: GTAC
Blogs from testing philosophers
eg: James Bach
Testing sites
eg: StickyMinds

30. Personal Learning Experience
Appium
Eg: GTAC 2013 - Automation for Mobile Apps by Jonathan Lipps
New ideas
Eg: GTAC 2014 - “Take out flaky tests from CI. Put it back when they are
stable. Critical tests should never be taken out” by Ankit Mehta
“Turn off a feature that is buggy” by Ankit Mehta

31. Spike it!

32. Sharing is Caring
• Social media
• Blog
• Github
• Forums
• Stack Overflow

33. Example: Blogging

34. Enjoy!

35. THANK YOU!
Chuan Chuan Law
www.chuanchuanlaw.com