PORTFOLIO

Contact

PORTFOLIO

Testimonials

About

Contact

QA TESTING

QA Engineer Kris Kosta

QA TESTING

QA Engineer Kris Kosta

QA TESTING

QA Engineer Kris Kosta

My responsibility is to ensure that our products meet the highest standards of quality and are ready for the public.

OUR PROCESS

Quality assurance
testing can be boiled
down to two modes

Quality assurance testing can be boiled down to two modes

1

Smoke testing features:

Smoke testing
features:

To be one week behind the dev team, testing new builds and resolved tickets to verify fixes. And updating with bug reports and new tickets.

2

End-to-end testing everything:

End-to-end testing
everything:

Conduct a full end-to-end test for delivery. Then deliver a full report of each specific build, making sure the product is ready to face the public.

TESTING METHODS

Functional Testing

Verifying that each function of the software application behaves as intended.

Example: testing player movement, picking up tools, ensuring that surfaces are free of imperfections that might cause interference with the player, and verifying that the grapple hook functions correctly.

Verifying that each function of the software application behaves as intended.

Integration Testing

Verifies that the newly integrated components function correctly together and detect any issues arising from their integration.

Example: When the dev pushes a new build, the new features are double checked to ensure functionality.

Verifies that the newly integrated components function correctly together and detect any issues arising from their integration.

Example: When the dev pushes a new build, the new features are double checked to ensure functionality.

Regression Testing

Ensures that previously working functionalities remain unaffected by any new changes or updates in the software.

When the dev pushes a new build of the program, functionalities are re-tested to ensure new implementations have not interfered with previously working functions.

Ensures that previously working functionalities remain unaffected by any new changes or updates in the software.

When the dev pushes a new build of the program, functionalities are re-tested to ensure new implementations have not interfered with previously working functions.

End-to-end Testing

Testing the full program start to finish. Testing every level, every feature, and every component to ensure the product is flawless.

Performance Testing

Performance Testing aims to identify performance bottlenecks, potential issues, and areas for optimization. The program is measured by its responsiveness, stability, scalability, and resource usage.

Performance testing typically involves the following types of testing:

Load Testing

This helps us Determine how the system performs under typical conditions. Load testing evaluates the behavior of a system when subjected to normal or expected workloads.

Stress Testing

Find software's limits by pushing it beyond its normal capacity, helping identify breaking points, crashes, or performance degradation.

Soak/Endurance Testing

Testing the system's behavior under sustained usage over an extended period. This helps identify issues of performance degradation over time.

Scalability Testing

Scalability testing measures how the application handles increasing workloads. This test determines the system's ability to scale up or down with new integrations. This identifies potential bottlenecks and performance degradation.

Performance Profiling

Performance profiling involves analyzing the software's resource utilization, such as CPU, memory, disk usage, or network bandwidth. It helps identify potential bottlenecks, inefficient code, or areas for optimization.

My responsibility is to ensure that our products meet the highest standards of quality and are ready for the public.

My responsibility is to ensure that our products meet the highest standards of quality and are ready for the public.

My responsibility is to ensure that our products meet the highest standards of quality and are ready for the public.

OUR PROCESS

OUR PROCESS

Quality assurance testing can be boiled down to two modes

Quality assurance testing can be boiled down to two modes

1

1

Smoke testing features:

Smoke testing features:

To be one week behind the dev team, testing new builds and resolved tickets to verify fixes. And updating with bug reports and new tickets.

To be one week behind the dev team, testing new builds and resolved tickets to verify fixes. And updating with bug reports and new tickets.

2

2

End-to-end testing everything:

End-to-end testing everything:

End-to-end testing everything:

Conduct a full end-to-end test for delivery. Then deliver a full report of each specific build, making sure the product is ready to face the public.

Conduct a full end-to-end test for delivery. Then deliver a full report of each specific build, making sure the product is ready to face the public.

TESTING METHODS

TESTING METHODS

Fu﻿nctional Testing

Fu﻿nctional Testing

Fu﻿nctional Testing

Integration T﻿esting

Integration T﻿esting

Integration T﻿esting

Re﻿gression Testing

Re﻿gression Testing

Re﻿gression Testing

End﻿-to-end Testing

End﻿-to-end Testing

End﻿-to-end Testing

Performance Testing

Performance Testing

Performance Testing

Load﻿ Testing

Load﻿ Testing

Stress T﻿esting

Stress T﻿esting

Soa﻿k/Endurance Testing

Soa﻿k/Endurance Testing

Scalability Testing

Scalability Testing

Performance Profiling

Performance Profiling

Quality assurance
testing can be boiled
down to two modes

Smoke testing
features:

End-to-end testing
everything:

Functional Testing

Functional Testing

Functional Testing

Integration Testing

Integration Testing

Integration Testing

Regression Testing

Regression Testing

Regression Testing

End-to-end Testing

End-to-end Testing

End-to-end Testing

Load Testing

Load Testing

Stress Testing

Stress Testing

Soak/Endurance Testing

Soak/Endurance Testing