Process

Years of successful performance at the global market of software QA services helped us accumulate expertise and create transparent and effective process of cooperation with clients.

 

Service Lead Message

DSC_66881
Irina
Alabugina

QA Project Coordination

brackets_gray2

I will be glad to discuss your project, brainstorm how QA can improve your development and keep the end users happy.

DSC_66881
Irina
Alabugina

QA Project Coordination

Testing is not only about detecting the issues. It is about analyzing the bottlenecks and proposing solutions for delivery of a quality product. What is the right test coverage? Which documentation type is sufficient? Does the project need test automation?
Our approach to QA processes is to combine the industry best practices with our hands-on experience, client’s business needs and challenges.

QulixQA team is result-driven, therefore we:

load_testing

develop our own methods of building QA project teams

load_testing

build seamless and properly functioning processes with customers

load_testing

provide transparent workflow and its necessary adjustments

Workflow

1e

Team

Our dedicated teams are built based on the following criteria:


Technological profile 
When customers ask for a specific set of QA skills, we build teams keeping their demands in mind. In any other case, we analyze the task and share our vision of the technological stack and relevant experience of the candidates.

Qualification
As the team is ready to kick off, we verify that the client's expectations are met. Keeping this in mind, we send resumes of our staff and organize additional interviews, if necessary.

Being ready for onsite projects and business trips 
We verify if the project requires regular business trips and make sure our specialists are ready for that.

2e

Planning

After the team is ready, we plan the process:


Time overlap

We always negotiate over the most convenient work schedule for both of the teams. We ensure a 100% time overlap for the business partners in Europe and can offer a 50% overlap (4-5 hours daily) for the customers located in the US and Asia. If necessary, more overlapping hours are negotiable.

Communication flows
They are established to provide seamless communication within a new distributed structure. At this stage, we also agree upon the deсision makers, timelines, responsible persons and more.

Onboarding and sharing expertise 
Depending on the project complexity, we conduct a set of onsite workshops at the customer’s company to share expertise with all of the team members and beef up the overall team spirit.

3e

Execution


Our key principle is to make the workflow transparent for both parties. The client’s team and the stakeholders are always aware of the tasks, priorities, and progress. We use well-developed process infrastructure and popular convenient tools, like:

jira test center confluence

We provide detailed reports on project milestones, schedule status online meetings, and calls.

Documents

Testing plans

load_testing
They clearly specify project goals and objectives, the scope of work, components under test, testing KPIs, and documentation. See example →

Reports

load_testing
They include software quality assessment, details on the test coverage and the list of revealed defects (critical, medium or minor). See example →

Test cases

load_testing
Test cases consist of detailed information about specific tests including system state description before the test, the entry data, actions, the exit data, etc.

See example →

More

We also create additional reports such as benchmarking on development team performance, the number of defects fixed per sprint, and etc.)

Checklists

load_testing
Checklist is a high-level document used for simpler systems and faster delivery. It specifies components under test along with the results (passed or failed), and doesn’t specify the testing techniques used. See example →

Checklists

load_testing
Checklist is a high-level document used for simpler systems and faster delivery. It specifies components under test along with the results (passed or failed), and doesn’t specify the testing techniques used. See example →

More

We also create additional reports such as benchmarking on development team performance, the number of defects fixed per sprint, and etc.)

Start looking
for bugs

We take a full-service approach to every
client and project, meaning our testing
process is streamlined and effective.

scema4

scema1

scema2

scema3

scema3