wave-1 wave-2

Manual Testing

We verify end-to-end business processes in systems and applications.

The manual testers take on the role of the target user. They try to predict any actions and errors they may make while working with the product.
  • we check the requirements in the early stages of the product's life,
  • we perform complex scenarios to check the simultaneous interaction of all parts of the systems with each other,
  • we disclose software errors.

Build confidence in your brand by removing bugs at an early stage of project life. Let users enjoy a bug-free product.

We do

We do

  • Web application tests
  • Mobile app tests: IOS + Android
  • Cor app tests – banking applications
  • CRM (Customer Relationship Management) application tests – online stores
  • Embedded system tests
  • Testing of business processes – ERP, SAP, Siebel, PeopleSoft
M Test

Manual test steps

<b>Reviews</b>
Reviews

Tests performed before the first line of code is created. They are tasked with finding discrepancies and inaccuracies of documentation with business assumptions and reviewing the mock-ups, whether they cover all possible actions provided for the system.

<b>Integration tests</b>
Integration tests

First tests performed by a tester during project life. They check whether the elements of the system created so far cooperate with each other.

<b>System tests</b>
System tests

The most important and time-consuming tests during the development. They are designed to check that all application modules work together in a test environment and follow all instructions required by the documentation. During system testing, a number of non-functional tests, such as performance, safety and usability, are also performed.

<b>Acceptance Test</b>
Acceptance Test

alpha and beta tests. Tests carried out by the target users in or near the target environment. These are often exploratory tests (performed without previously prepared scenarios), aimed at testing basic system functionalities.

P Manual test

Process of carrying out manual tests

01

White-box tests. Analysis of requirements, mock-ups and design assumptions and code browsing by programmers.

02

Unit tests during software development

03

Create test scenarios in the form of user stories – examples of application use or specific modules

04

Carrying out tests taking into account all scenarios created

05

Report all bugs and application failures for improvement

06

Implementation of improvements made by developers

07

Tests confirming the repair of a defect

08

Re-testing the entire application to exclude the negative impact of the patch on the operation of the application

09

Alpha and beta tests performed by target users

Collaborative models

Customer teams

A service dedicated to customers with project teams. We provide quick support with missing competences.

Teams at B2Bnetwork

We can use our hardware and software. We implement a system that allows you a continuous monitoring

Billing models

Fixed - Price

Specific scope of the project, requirements, lead time and price.

Time&Material

The project budget depends on the work needed to be done.

Time&Material with a limit

We determine the scope of work with a budget limit and lead time.
CTA

See if we can help you with software tests.

Make an appointment for a short, several-minute conversation, during which we will jointly check whether cooperation with us will bring changes for your project.

Do you have any questions?

Contact us!

Artur Twardowski Business Development Manager +48 795 022 922