Testing Types



Load and Performance

UX and Usability

Test design


Regression testing



QA audit

Functional Testing

Functional testing is aimed at verification of declared functionality implementation.

By studying requirements and specifications, we prepare a set of scenarios and test cases.

Our team will perform complex testing and find problems before your customers encounter them.

Types of Functional testing are:

  • Unit Testing
  • Smoke Testing
  • Sanity Testing
  • White/Black box Testing
  • User Acceptance Testing
  • Go to top

Compatibility testing

We will check whether your software is capable of running on different hardware, operating systems, applications, network environments or mobile devices.

It’s basically a check of how well a system performs in a particular environment.

Types of Compatibility testing are:

  • Backward/Forward compatibility
  • Operating Systems
  • Hardware
  • Software
  • Network
  • Browser
  • Devices
  • Mobile
  • Go to top

Load and Performance testing

We use it to determine how fast a system performs under a particular workload.

It can serve different purposes such as checking whether the system meets performance criteria.

We can compare two systems to find out which of them performs better. Or it can detect what part of the system or workload causes the system performance degradation.

When to use performance testing:

  • To Identify bottlenecks such as database configuration
  • To Determine if a new release is ready for production
  • To Gather metrics useful for tuning the system
  • To Improve user experience
  • To Increase revenue

Go to top

UX and Usability testing

Usability testing reveals whether users feel comfortable with your application according to different parameters – the flow, navigation and layout, speed and content – especially in comparison to prior or similar applications.

Usability testing includes the following five components:

  • Memorability
  • Learnability
  • Satisfaction
  • Efficiency
  • Errors

Go to top

Test design

Test design should start the moment the system requirements have been approved and baselined.

We are creating a set of inputs for given software that will provide a set of expected outputs.

The idea is to ensure that the system is working good enough and it can be released with as few problems as possible for the average user.

The test design changes/adapts during the system development life cycle iterations.

Well designed test suites will provide an efficient testing.

Test Case Requirements:

  • Need to ensure 100% Coverage
  • Repeatable and self-standing
  • Design with End User in Mind
  • Simple and Transparent
  • Avoid test repetition
  • Go to top

Requirements and Documentation testing

We go through the Requirement document in order to identify the testable requirements.

Activities to be done in Requirement analysis phase:

  • Identifying the testing techniques and testing types
  • Analyzing the System Requirement Specifications
  • Preparing a Requirement Traceability Matrix
  • Identifying the testing environment
  • Prioritizing the features testing

Deliverables (Outcome) of Requirement analysis phase are:

  • Requirement Traceability Matrix (RTM)
  • Automation feasibility report

Go to top

Security testing

We check if the application is vulnerable to attacks, if anyone hacks the system or logs in to the application without any authorization.

It is a process to determine that an information system protects data and maintains functionality as intended.

  • Non-repudiation
  • Confidentiality
  • Authentication
  • Authorization
  • Availability
  • Integrity

Go to top

Regression testing

When any modifications are done to the application code it can bring unexpected issues.

It is very important to test whether the existing functionality is intact.

Regression helps in maintaining the quality of the product along with the new changes.

Regression testing is used when:

  • Any performance related issue is fixed
  • Any new feature is added
  • Any enhancement is done
  • Any bug is fixed

Go to top

Compliance testing

We will evaluate your project compliance with the guidelines of the specific platform – Apple, Google, Amazon, Microsoft, Sony, Nintendo, etc.

Our team will pinpoint any drawbacks in standards implementation.

It’s basically an audit of a system carried out against known criteria.

Benefits of Compliance Testing:

  • Provides appropriate utilization of standards
  • Assures the proper implementation of specifications
  • Assures that interfaces and functions are working as expected
  • Go to top

QA Audit & Consulting

SnoopGame QA offers its expertise in providing an objective quality evaluation of your internal processes and products intended for release.

Our specialists do a thorough analysis and research, in order to identify the gaps in the QA process and what could be improved.

QA Audit covers numerous areas, which include, but are not limited to:

  • Review of QA resources quality of work performed
  • Review of process management structure
  • Quality of project documentation
  • Relevant testing process review
  • QA project strategy monitoring
  • Building an Improvement Scope
  • Testing coverage review
  • Ticket Management

QA Audit Executions Types

1. Regular/Planned

Scheduled for regular review to guarantee quality assurance process monitoring, as well as help to keep the customer informed on the quality of the process itself.

2. Project-based/Project stage-based

Provided on different product stages. In this way, our customers can monitor any separate project stage and see the big picture of a project.

3. Episodic/Custom

Intended for companies that ask for a single QA audit execution.

Go to top