QA part 2

Testing From Beginner to Expert
by APIGM
Charles Cao@apigm.org
01.20. 2017

Presenter
 Charles Cao,
 Senior QA Engineer, Business Owner.10+ years working experience, He
promoted to senior QA from an intern by only 3 years.

Agenda
 Introduction: Path To an Great Quality Assurance Engineer
 What is Quality Assurance
 How to start as an Quality Assurance Engineer
 When you are ready for a Testing job?

Path To an Great Quality Assurance
Engineer

What is Quality Assurance
It is the process used to identify the correctness, completeness and quality of
developed computer software.
It is the process of executing a program/application under positive and negative
conditions by manual or automated means. It checks for the :-
 Specification
 Functionality
 Performance

OBJECTIVES
Uncover as many as errors (or bugs) as possible in a given product.
Demonstrate a given software product matching its requirement
specifications.
Validate the quality of a software testing using the minimum cost and efforts.
Generate high quality test cases, perform effective tests, and issue correct
and helpful problem reports.

Testing Methodologies
 Black box testing
 No knowledge of internal program design or code required.
 Tests are based on requirements and functionality.
 White box testing
 Knowledge of the internal program design and code required.
 Tests are based on coverage of code statements, branches,
paths, conditions.

Testing Type
 Manual Testing
 Automated Testing

Demo
 Manual testing
 GOOGLE page
 Pinpin Market
 Automation Testing
 Selenium UI validating google
 Pinpin Market online validation
 Performance Test

Workshop Design
 Web manual validation
 Test case creation
 Bug Reporting
 Selenium IDE
 Selenium Automation with Java
 Cucumber Framework
 Rest API Testing
 Performance Testing

Test Plan
 It is a systematic approach to test a system i.e. software. The plan typically
contains a detailed understanding of what the eventual testing workflow will
be.

Test Case
 It is a specific procedure of testing a particular requirement.
 It will include:
Identification of specific requirement tested
Test case success/failure criteria
Specific steps to execute test
Test data

Junit
 A tool for test-driven development

Writing methods in TestCase
 Pattern follows programming by contract paradigm:
 Set up preconditions
 Exercise functionality being tested
 Check postconditions
 Example:
public void testEmptyList() {
Bowl emptyBowl = new Bowl();
assertEquals(“Size of an empty list should be zero.”,
0, emptyList.size());
assertTrue(“An empty bowl should report empty.”,
emptyBowl.isEmpty());
}
 Things to notice:
 Specific method signature – public void testWhatever()
 Allows them to be found and collected automatically by JUnit
 Coding follows pattern
 Notice the assert-type calls…

Assert methods
 assertTrue(String message, Boolean test)
 assertFalse(String message, Boolean test)
 assertNull(String message, Object object)
 assertNotNull(String message, Object object)
 assertEquals(String message, Object expected, Object actual) (uses equals
method)
 assertSame(String message, Object expected, Object actual) (uses == operator)
 assertNotSame(String message, Object expected, Object actual)

XPath in Selenium
 http://www.guru99.com/xpath-selenium.html

 // : Select current node.
 Tagname: Tagname of the particular node.
 @: Select attribute.
 Attribute: Attribute name of the node.
 Value: Value of the attribute.
Xpath=//tagname[@attribute='value']

 http://demo.guru99.com/v1/

QA part 2

More Related Content

What's hot (18)

Similar to QA part 2 (20)

More from Wayne Weixin (7)

Recently uploaded (20)

QA part 2