Phoenix - Your AI AssistantLogin Testing & Data Extraction Automation
- Posted:
- Proposals: 26
- Remote
- #4500240
- Expired
Lahore 
Description
Experience Level: Entry
Deadline is 23.00. 2026-06-05.
We are looking for an experienced automation developer to build a solution that can process a list of authorized test accounts, verify login credentials, and extract specific account information for reporting purposes. The project is intended for legitimate QA, testing, or account-management workflows and must comply with all applicable laws, platform terms of service, and authorization requirements.
The tool should accept a CSV or TXT file containing usernames or email addresses along with passwords. It should attempt to log into each account, determine whether the login was successful or failed, and record the result. For successfully authenticated accounts, the tool should collect available information including shipment totals, country counts (for example, GB: 2, US: 9), account type (Individual or Business), account status (Active or Inactive), account country, account address, company name, and whether an active payment method is attached to the account.
The solution must not collect, display, store, export, or process any sensitive payment information. This includes credit card numbers, expiration dates, CVV codes, bank account details, or payment credentials. The only payment-related information that should be returned is a simple Yes or No indicator showing whether an active payment method exists.
The final output should be provided as a CSV report containing the username, login result, shipment total, country count, account type, account status, account country, account address, company name, payment method present (Yes/No), and any notes or error messages encountered during processing.
OB2 is the preferred technology, The solution should include proper error handling, retry logic where appropriate, clear documentation, and complete source code delivery.
The final deliverables should include the full source code, setup instructions, documentation, an example output CSV file, and a demonstration using authorized test accounts.
We are looking for an experienced automation developer to build a solution that can process a list of authorized test accounts, verify login credentials, and extract specific account information for reporting purposes. The project is intended for legitimate QA, testing, or account-management workflows and must comply with all applicable laws, platform terms of service, and authorization requirements.
The tool should accept a CSV or TXT file containing usernames or email addresses along with passwords. It should attempt to log into each account, determine whether the login was successful or failed, and record the result. For successfully authenticated accounts, the tool should collect available information including shipment totals, country counts (for example, GB: 2, US: 9), account type (Individual or Business), account status (Active or Inactive), account country, account address, company name, and whether an active payment method is attached to the account.
The solution must not collect, display, store, export, or process any sensitive payment information. This includes credit card numbers, expiration dates, CVV codes, bank account details, or payment credentials. The only payment-related information that should be returned is a simple Yes or No indicator showing whether an active payment method exists.
The final output should be provided as a CSV report containing the username, login result, shipment total, country count, account type, account status, account country, account address, company name, payment method present (Yes/No), and any notes or error messages encountered during processing.
OB2 is the preferred technology, The solution should include proper error handling, retry logic where appropriate, clear documentation, and complete source code delivery.
The final deliverables should include the full source code, setup instructions, documentation, an example output CSV file, and a demonstration using authorized test accounts.
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
Before we proceed, I have a few important questions:
1. Which website/platform are these authorized test accounts for?
2. Does the login process include CAPTCHA, OTP, or 2FA verification?
3. Approximately how many accounts need to be processed in a single run?
4. When you mention OB2, are you referring to a specific framework or automation platform?
-
Can you attach 1- 2 sample records of input file?