QA Area Overview


Who am I?

Note: tell people who you are.

What is software testing?

  • By definition: Software testing is an investigation conducted to provide stakeholders information about the quality of the product or service under test.
  • For me: It is to make sure that everything works as expected, having the less possible amount of bugs. 

Why is software testing necessary in the development process?

  • Software testing improves the product's quality.
  • Allows the product to get metrics about the product's quality.
  • Developers can't cover all possible scenarios.
  • I would say that its all about return on investment.
  • Different types of testing are required depending on the project stage.
  • Someone needs to make sure that everything works as expected.

QA path careers

Lets talk first about what every QC should do

  • Be aware of the expected behaviour and what to expect from the app.
  • Be aware of who is gonna be the end user.
  • Be aware of how will the product be sold.
  • Define the testing scope based on requirements. (QA)
  • Define acceptance criteria if required.
  • Write the test case suite based on all the points above.
  • Keep them updated with the latest features.
  • Track the bugs in a bug tracker (Jira,Bugzilla,Mantis, Pivotal, etc).
  • Be passionate :)

I would name three big groups


  • Functional


  • Non Functional


  • Business Analyst


Functional Testing


Functional testing is a quality assurance process that bases its test cases on the specifications of the software component under test. Functions are tested by feeding them an input and examining the output, and internal program structure is rarely considered. Functional testing usually describes what the system does. Functional testing tests a slice of functionality of the whole system.

Some examples are:

Non Functional Testing


Non-functional testing is to test a software application or system for its non-functional requirements: the way a system operates, rather than specific behaviours of that system. This is contrast to functional testing, who tests against functional requirements that describe the functions of a system and its components.

Some examples are:

Businness Analyst


A business analyst is someone who analyses an organization or business domain (real or hypothetical) and documents its business or processes or systems, assessing the business model or its integration with technology.

There are at least four types of business analysis:

  1. Strategic planning – to identify the organization's business needs
  2. Business model analysis – to define the organization's policies and market approaches
  3. Process design – to standardize the organization’s workflows
  4. Systems analysis – the interpretation of business rules and requirements for technical systems (generally within IT)

Certifications and education




Benefits for professionals


  • Authorized to use the “Certified Tester” logo (specifying the level of certification)


  • Whole of career path support, from Foundation to Expert level


  • International recognition of acquired competencies and skills

Benefits for Companies


  • ISTQB® certification can provide a competitive advantage for companies, promising a higher level of reliability of the applications being developed due to efficient and cost effective testing practices derived from the ISTQB® competencies


  • ISTQB® has defined a “Partner Program” for companies that engage a large number of certified testers


  • Consulting companies with certified staff can offer higher-level services to customers, increasing revenues and brand value

Test Cases


 A test case is basically a bunch of instructions that everyone (And when I say everyone, I mean everyone) should be able to follow, no matter the previous knowledge of the app or the involved technology, that will determine if the result of all of those steps is the expected one or not.

Step to follow Expected result
Open a web Browser The web browser is opened
Browse Google site is displayed
Close the browser by using the "x" in the upper right corner The browser is closed successfully

User Stories


  • User stories are short, simple descriptions of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system. They typically follow a simple template:

As a <type of user>, I want <some goal> so that <some reason>.


  • It is possible that some user stories are so huge, so this will force us to lose detail. The most common solution for this scenario is by splitting a user story into multiple, smaller user stories.

Lets see some action :)

Thank you!!!