ANALISTA DE TESTES JUNIOR/PLENO  

Nível Profissional.
Pleno Nível Acadêmico.
Ensino Médio Completo Áreas de Atuação Profissional.
TI - Projetos Descrição.
RFP - [Mobile Payment] Pre-launch scaled testing We are looking for partners to execute below scope of work for one of our customers.
What we need from our partners in response.
• Understanding of scope • Assumptions • Dependencies • Summary of proposed solution • Timelines to execute • Total cost for defined scope If there are any questions, please let us know.
Technical Scope This document aims to lay out the scope for tests required prior to launching Mobile Payment with 16 banks in Brazil Goals • Test if App account linking and payment flow in App is working correctly with a pre-determined list of 16 financial institutions (also referred to as “Banks”) • Identify any potential bugs that may occur post App-Bank integration Scope Object of testing • 16 banks • 5 users / testers per bank that fill the tester requirements as described below • Each user / tester will run a set of instructions in the tests that compose roughly ~10 different transactions.
• There will be 3 rounds of tests occurring between Nov 25th and Feb 28th.
Stages 1.
[Now until Dec-] Tester recruitment & set-up a.
Partner to recruit testers that fill the following requirements • Have a bank account from the list of banks • Have an android phone from this list of allowed devices for testing (at least 5 different types of devices should be used across the testers) • Have a gmail account ready to be used in App in Brazil with a Brazil billing address (note that 1 person can have more than on bank account and more than one gmail accounts, but the same tester should not have more than 3 gmail accounts and no more than 5 bank accounts linked to App to avoid Risk-flags in the process) These are NOT requirements for testers.
location of the testers, income, age, gender, language fluency (only PT is required).
2.
Partner to provide the list of gmail accounts & banks associated with each tester in the format provided.
allowlist these testers (please note this is the only personal information from testers required in this study and gmail accounts should be created specifically for the purpose of testing so they are not treated as PII) 3.
Partner to set-up testers for tests o Tester device & account checklist o Tester to complete account linking & report any issues as per Account link instructions (please note account linking is already a robust testing that may require bug resolution) 4.
To provide bug resolution for any account link issues During this phase, we may reach out to partner to clarify questions and ask for one-off additional testing.
2.
[Dec-9-24 to Jan ] Test Round #1 All test rounds (1, 2 and 3) will occur similarly as follows and detailed in the Round test instructions o Partner to confirm instructions to follow (PT) o [Week 1] Partner to execute tests with testers according to test plan o Partner to provide feedback from testers in the template format (ENG) o Based on customer review of test results, customer may request clarifications.
Our partner will need to engage testers for clarification and stress test 3.
[Jan13 to ] Test Round #2 4.
[Feb 3 to ] Test Round #3 5.
Final Stage, March-.
additional test rounds, if required & final bug resolution During this phase, we may reach out to partner to clarify questions and ask for one-off additional testing.
However, this is expected to be lightweight and would not require more than 10 tests through the month Habilidades.
Work Dynamics • The partner will arrange testers who have back accounts with different banks • The partner will arrange testers who have commonly used Android devices.
List of devices will be provided later.
One user / tester can have just one device but different testers should have different devices to provide coverage across several devices.
• The partner should have one single PoC based in Brazil and English speaking to provide weekly updates, clarifications and consolidation of all feedback • Weekly VC meetings between working group • HCL will only fund P2M transactions required for testing (amounts to provided later, but assume ~BRL in total transaction amount).
P2P transactions can be reverted between payer and receiver, when required.