Technical Alignment - Tester/QA

Full Name: Date: 12/05/2023

The person in the Tester/QA role has a mission to ensure that the solution meets Sprint objectives and expected
quality. We then prepared some technical and practical questions to align these expected results.

Kognit appreciates your interest and effort in answering this test so that we can align the technical points.

1. Technical Skills Questions for Quality Assurance and Functional Testing

a) You are participating in the development of a new product through a multidisciplinary team. If you are responsible
for ongoing Sprint QA and testing, what do you consider relevant to address in Sprint Planning?

It's important take into account the estimated hours that the tests will take, estimate the hours that
the requirements gathering will take, have a margin of time reserved for possible bugs and questions
during the tests and estimate the time that it will take to write the scenarios.

b) What do you think are the most important work items for testing to be considered and planned in order to reach a
Sprint Objective.

I consider it more important to consider all the tests that were planned in planning and refinement,
possible stories that can be introduced, a margin of time for bugs or adjustments. A very well feed
testing environment with masses of information, good knowledge of business rules and the tool,
clearing all doubts before starting writing and gathering requirements and a good team relationship
for the correct progress of tests in the sprint.

c) Once we have a clear Sprint Objective, describe the process you would follow to create effective test cases.
 Technical Alignment - Tester/QA

Full Name: Date: 12/05/2023

First understand the requirements and business rules that will be applied in the tests, with which other
APIs and system tools the respective tests are working together and have an end user view so that the
result has an expected functionality, but also a purpose clear and objective for the user, because in
addition to the technical part we have to have a user vision.

d) Suppose you have identified a bug in the software during testing. Please describe the process you would follow to
report and track this bug until it is resolved.

Document and show all the necessary steps to reproduce the bug, the technical analysis that we can predict
from the tests to help the developers, clearly show the error and carry out a retest plan for the future
when the bug is resolved.

e) What are the main types of tests you would consider for a web app? Briefly explain each of them.

In addition to the usual tests, the following are essential:

Unit tests: known as a white box, its purpose is to test the code in parts and/or blocks.
Functional Tests: or black box, where we test the system's functionalities using a point of view aimed at
the end user, with a less technical view and more focused on the user who will use the tool on a daily
basis.
Integration tests: where we test the integration of tests and their functionality with the container and the
system.

f) How would you approach testing a complex system that involves integration with multiple components and external
systems?
 Technical Alignment - Tester/QA

Full Name: Date: 12/05/2023

Writing scenarios that cover the external and internal environments, planning the possible daily steps
of the user manipulating the tool, the possible scenarios involving the entire integration of the
application and the components that work both individually and those that work together.

g) Describe the approach you would take to regression test software after implementing new functionality.

A good regression test covers all the stories that were tested, with good masses that cover all the scenarios
involved.

2. Practical Test

Platform currently has a screen where you are able to manage team members as follows:
 Technical Alignment - Tester/QA

Full Name: Date: 12/05/2023

Consider you are the Administrator (Owner) user, so you have the right to perform any operation available
● As the Owner you can transfer your Ownership to another user;
● As the Owner you can invite new members;
 Technical Alignment - Tester/QA

Full Name: Date: 12/05/2023

a) Below we have a screen (mockups / prototype) that allow you sending an invitation to a new member. Please
describe below the scenarios you would test to make sure the objective was delivered by the team and to ensure
that validations are done to avoid issues during the operation. You need to cover since the first step where the
Owner sends the invitation to the new member though Email, until the new user's first access to the platform.

Certification and testing scenarios (it can be one or more scenarios to validate):

Full Name:
Scenario to be validated: Email address validation
Expecteds results
It is expected that the system validate that the email
address is valid and/or existing
It is expected that the system validade that the email
address is duplicated and that already exist
It is expected that the system validate the member user’s
team and if the email entered is already a team member. If
is already a member, the system will show a message that
will advert the validation
Technical Alignment - Tester/QA
Date: 12/05/2023
How to perform the test
Scenario: Enter an invalid email address
Given that the user is an Administrator
When entering an invalid or non-existent email address in the
email address field
Then the system will not recognize the entered email address
Scenario: Enter a duplicate email address
Given that the user is an Administrator
When entering a duplicate email address in the email address
field
Then the system will recognize that the email address is already
inputed
Scenario: Enter an email address that is already a member of the
team
Given that the user is an Administrator
 Technical Alignment - Tester/QA

Full Name: Date: 12/05/2023

When entering an email address that is already an user member

of the team

Then the system will detect that the email address is already a
member of the team
Scenario to be validated: Search by role field validation
Expecteds results How to perform the test
It is expected that the system validate that the role is valid Scenario: Enter an invalid role
and/or existing
Given that the user is an Administrator

When entering an invalid or non-existent role name in the

‘Search by Role’ field

Then the system will not recognize the entered role name
It is expected that the system show the picklist of valid Scenario: Enter a valid role
role(s) that the user write, if it’s an existing role
Given that the user is an Administrator

When entering a valid role name

Scenario to be validated: Validate that the objective was delivered
It is expected that the Administrator get a view that the
invitation has reached the end user
Then the system will recognize the entered role name and will
show the role if it's existent
Scenario: Ensure that the invitation is sent to the member
Given that the invite is already sent
 Technical Alignment - Tester/QA

Full Name: Date: 12/05/2023

When the invitation reaches the member

Then a delivery validation and/or acceptance will be sent to the

Administrator/invitation sender

Scenario to be validated: Validate the first access of the new user member
Validate that the first access of the new team member will Scenario: Receive a validation of the new user's access in the
succeed members area, through the invitation

Given that the invite is already sent

And the user is already accepted the invite

When the new member access the platform as a new team

member

Then a delivery validation will be sent to the administrator,

reporting the new user access

b) Now, considering it is also possible transfering an Owner rights to someone else in a safe way, please try to write
some Steps of a scenario that would cover this operation. It is important to consider a second certification that the
Owner is the one who is performing the transferring to another person.

Full Name:
Certification and testing scenarios (it can be one or more scenarios to validate):
Scenario to be validated: Email address validation
Expecteds results
It is expected that the system validate that the email
address is valid and/or existing
It is expected that the system validade that the email
address is duplicated and that already exist
It is expected that the system validate the member user’s
team and if the email entered is already a team member. If
Technical Alignment - Tester/QA
Date: 12/05/2023
How to perform the test
Scenario: Enter an invalid email address
Given that the user is an owner or a valid user to perform the
operation
When entering an invalid or non-existent email address in the
email address field
Then the system will not recognize the entered email address
Scenario: Enter a duplicate email address
Given that the user is an owner or a valid user to perform the
operation
When entering a duplicate email address in the email address
field
Then the system will recognize that the email address is already
inputed
Scenario: Enter an email address that is already a member of the
team
 Technical Alignment - Tester/QA

Full Name: Date: 12/05/2023

is already a member, the system will show a message that Given that the user is an owner or a valid user to perform the
will advert the validation operation

When entering an email address that is already an user member

of the team

Then the system will detect that the email address is already a
member of the team
Validate the user permission Scenario: Enter na email address with a not autorized user

Given that the user is not an owner or a valid user to perform the
operation

When entering an email address

And try to validate the information

Then the system will return that the user is not permited to do
this action
Scenario to be validated: Search by role field validation
Expecteds results How to perform the test
It is expected that the system validate that the role is valid Scenario: Enter an invalid role
and/or existing
Given that the user is an owner or a valid user to perform the
operation
 Technical Alignment - Tester/QA

Full Name: Date: 12/05/2023

When entering an invalid or non-existent role name in the

‘Search by Role’ field

It is expected that the system show the picklist of valid
role(s) that the user write, if it’s an existing role
Then the system will not recognize the entered role name
Scenario: Enter a valid role
Given that the user is an owner or a valid user to perform the
operation

When entering a valid role name

Then the system will recognize the entered role name and will
show the role if it's existent
Validate the user permission Scenario: Enter a role with a not permited user

Given that the user is not an owner or a valid user to perform the
operation

When entering a role name

And try to validate the information

Scenario to be validated: Validate that the objective was delivered
It is expected that the owner or a valid user that could be
the sender of the invite get a view that the invitation has
Then the system will return that the user is not permited to do
this action
Scenario: Ensure that the invitation is sent to the member
 Technical Alignment - Tester/QA

Full Name: Date: 12/05/2023

reached the end user, with the description of the permited Given that the invite is already sent
user that sent the invite
When the invitation reaches the member

Then a delivery validation and/or acceptance will be sent to the

Administrator/invitation permited sender
Scenario to be validated: Validate the first access of the new user member
Validate that the first access of the new team member will Scenario: Receive a validation of the new user's access in the
succeed members area, through the invitation

Given that the invite is already sent

And the user is already accepted the invite

When the new member access the platform as a new team

member

Then a delivery validation will be sent to the owner or a valid

user that sent the invite, reporting the new user access