Pricing Estimator

Hello! We developed this tool to provide price estimation. We understand that each company has its own requirements for tests, that's why at the end of this estimative you can call upon one Base2 consultant to get in touch to provide a more accurate budget.

  • Your system is having many bugs in the hands of the final user?
  • Are you getting a new system, but do you need to evaluate it to see if it will work completely?
  • Does your company perform constant system updates and need to ensure that it will continue to function normally?
Then its is very likely that you will find the best solution clicking below.
  • Your application is used by hundreds or thousands of users at the same time?
  • Are there times when your application is slow?
  • Your system is showing low performance and you can’t find what is happening?
Click below and see a proper solution for your problem!
  • Need to understand how your application will work in real-world environment?
  • Do you have a low budget and a lot of urgency to carry out the tests?
Then the better solution for you is Crowdtest: Tests performed by real users spread over the Internet using the Crowdsourcing model.
  • Does your application require a high level of confidentiality?
  • Only graduated professionals could test your system?
To understand you demanding, we offer certificated and qualified professionals to deliver accurate results.

Parameters – QA Outsourcing

The Test Factory involves specific processes to each customer profile. There is a very large number of variables that need to be treated in order to generate a proposal that is appropriate to each reality. Therefore, we ask you to provide us some information. Soon one of our commercial consultants will contact you to understand your software reality.

What your company needs?

Which application profile should be tested?

Please provide as many details as you can. Example: development platform, database, development team size if any, test team size if any, already use some test automation tool and, if you use which ones, and other possible informations.

Parameters – Load testing

How many flows should be executed?

What kind of test do you want to do?

What is the aim of the test?

The test execution should be delivered at what time?

Previous Proposal

Test Settings

The test setting involves all the planning, structuring of the execution environment, and the setup of the tool for the test execution. The first activity of this phase is the understanding of the scenarios that will compose the scope of the project and the environment to be used in the tests. Also, will be done the configuration of the tools to monitor the resources of the servers.

Mounting the Synthetic Charge

A system usage model will be generated, based on the expectation of use. This system usage model will consider the case-by-case flows identified together with the customer's team. Based on the elaborated model, the synthetic load will be developed, which consists in the creation of a base of requisition that can simulate the software using by its users. An additional activity will be the development of test execution scripts and data collection support. The simulation of the accesses will be done through a specific tool, a "robot" of tests. This tool runs a script designed to simulate a particular operation of the system. The test robot will control the virtual users who will be continuously accessing the application and collecting information such as response time. The end result of this step is the basis of requisitions that must be performed during the test execution and the test scripts, duly validated.

Test Execution

Consist in the using of testing tools to submit the synthetic loads to the system. Besides execution, it also contains the superficial analysis of the results collected.


This work involves the instrumentation of the Java code responsible for the back-end, in order to identify the contention points that occurred during the use of the system. The instrumentation will be performed with the support of profiling tools. Once the points of contention are identified, we will seek to know their causes. For this we will analyze the routines involved and even SQL’s clauses, taking into account the existence or not of table indexes.

Final Report Elaboration

With the tests results available, a detailed analysis will be done.Will be analyzed the response time data, volume of operations, flow and pages with greater response times. In this work we will also collect and analyze data usage of resources of servers, such as CPU, memory, network band, etc. A report will be elaborated containing the performance graphs utilization rate, CPU / memory / network / disk and the observation of the results.

Final Report Elaboration

With the tests results available, a detailed analysis will be done.Will be analyzed the response time data, volume of operations, flow and pages with greater response times. In this work we will also collect and analyze data usage of resources of servers, such as CPU, memory, network band, etc. A report will be elaborated containing the performance graphs utilization rate, CPU / memory / network / disk and the observation of the results.

Estimated Price


I want a proposal!

Send us more details about your demand. For example: development platform, database, using protocols, integration with others services or systems, and others.
Informe o maior número de detalhes que puder. Exemplo: plataforma de desenvolvimento, banco de dados, protocolos utilizados, integração com outros serviços ou sistemas etc.

Parameters – Crowdtest

How many cycles should be performed per month?

What is the profile of the application that should be tested?

Previous Proposal


In Crowdtest pay-per-bug one group of testers is recruited to find bugs at the client’s application. The types of bugs that are being considered in this proposal are:


Prevent the using of any functionality at the application.There is no exits or other alternatives to contour it. These faults need to be fixed before release a version to end consumer.


Violations that allows the user to perform some activity not allowed in the system. In this context, tester can perform basic attempts to access functions without permission and even code injection.


Produce a illogical or unexpected behavior in the application and the end result is different than expected.

Graphical User Interface (GUI)

Are those related to the graphical interface. Examples: misaligned components, incorrect interface rendering, inconsistent colors with style guide etc.


In this case, these are not bugs but suggestions to the software improvement. This suggestions are given based on the experience of the testers and the market standard.


Languages mistakes found in the application text. Each language problem is considered as text fault.


In the pay-per-test model of Crowdtest the work is divided as follows:
  • Test Analyst:
    • Responsible for specifying the tests and managing their execution by Crowdtest base of testers. Test Analyst Responsibilities:
      • Test Checklist Assembly
      • Setting up the tool of tests management
      • Setting up the tool to register the bugs
      • Validation of Evidences from Test Cases
      • Register of bugs
      • Clarification of testers doubts during the project.
      • Testers selection
  • Crowdtest Core Testers:
    • Responsible for the tests execution and the register of the test evidences in video.
To execute a pay-per-test project, the following steps are followed:
  • Setup
    • This step aims to prepare the project in the support tool of Crowdtest. We need to establish the parameters that will define the tests that will be done and consequently the failures/bugs that will be valid. Among these parameters we have:
      • Functionalities and/or interfaces of the target application that should be tested;
      • Web browsers;
      • Mobile devices
      • Operational systems
    • In addition to the parameterization of the projects, in this step are collected and provided support materials for the testers. Also, small guides are produced to instruct the testers.
    • In order for the results of this step to be produced with quality, the involvement of the client's team is extremely important. All information are gathered from documentation and meetings, either face-to-face or remote, with the client.
  • Specification
    • At this stage the test analyst of the project produces a simplified specification of the test cases that will be carried out in the project. This specification is in principle a test checklist, without step detailing. One or another test case can be detailed according to its complexity.
    • The resources for the assembly of this specification are: meetings with customers, user manuals, specification of tests produced by the client, and others.
  • Recruiting
    • At this step the Crowdtest team will be responsible for disclose, receive candidates and select the best profiles for the interest of the project
  • Execution
    • At this stage the test analyst divides the test cases among the recruited testers and track the project execution. If any tester is not performing satisfactorily, he is replaced immediately.
    • Each test case performed needs to be demonstrated in video and the result reported on the support tool defined by Crowdtest.
  • Validation and Bug Report
    • Each test case performed and evidenced in video is checked by the test analyst. If is found any nonconformity the test case is again executed.
    • Test cases that report bugs are analyzed by the test analyst who will open the bug register in a Crowdtest tool itself or in a customer-designated one.
    • The customer will receive at the end of the project the evidence of the test runs as well as the failure report. At this point he may question some evidences and ask for the re execution of some tests case.


Period: 1 month(1)
R$ 00,00
Period: 4 months(2)
R$ 00,00 / month
Period: 6 months(2)
R$ 00,00 / month
Period: 12 months(2)
R$ 00,00 / month
1. Payment method: 50% at the beginning of the project - 50% after delivery and approval of results
2. Payment every 5th business day or the 15th business day of the month