Skip to content
AgencyHandy
More
QA Docs
Testing Convention
1. Introduction
1.1 Purpose
This document outlines the conventions and best practices for testing at Onethread. It provides guidelines to ensure consistency, efficiency, and effectiveness in the testing process.
1.2 Scope
The scope of this document covers the conventions related to test case design, test data preparation, test execution, and defect reporting in testing.
1.3 Audience
This document is intended for the Quality Assurance (QA) team members, testers, and any other stakeholders involved in the testing process.
2. Testing Overview
2.1 Software Testing Definition
Software testing is a systematic process of evaluating and verifying that a software application or system meets specified requirements and functions correctly. It involves the execution of software/system components using manual or automated tools to identify defects, ensure the quality of the product, and provide stakeholders with confidence in its reliability.
2.2 Importance of Software Testing
Software testing is critical for ensuring the quality, reliability, and performance of software applications. It helps identify defects early in the development process, reduces the risk of post-release failures, and enhances the overall user experience. Testing also validates that the software meets functional and non-functional requirements.
2.3 When to Use Software Testing
Software testing is essential throughout the software development lifecycle, from the initial stages of development to post-release maintenance. It is particularly crucial during the following phases:
3. General Guidelines
In the realm of software testing, adhering to general guidelines is fundamental to ensure consistency, clarity, and efficiency throughout the testing process. This section outlines key principles that underpin the development and implementation of testing conventions within your organization.
3.1 Consistency:
Consistency serves as the cornerstone of effective testing conventions. By establishing consistent practices across all testing activities, team members can easily understand and follow the prescribed procedures. Consistency extends to various aspects of testing, including test case formats, execution procedures, and reporting mechanisms. When everyone adheres to the same conventions, it fosters a cohesive testing environment and reduces the likelihood of misunderstandings or errors.
3.2 Clarity:
Clear and comprehensible documentation is essential for successful testing. Test cases, procedures, and results must be articulated in a manner that is easily understandable by all stakeholders, regardless of their level of technical expertise. Ambiguity in test documentation can lead to misinterpretations and inconsistencies in testing outcomes. Therefore, it is imperative to employ concise language, standardized formats, and descriptive annotations to enhance clarity and facilitate effective communication among team members.
3.3 Efficiency:
Efficiency is another crucial aspect of testing conventions. While maintaining high standards of quality, testing processes should be optimized to maximize productivity and minimize time-to-market. This involves identifying and eliminating redundant or unnecessary steps, automating repetitive tasks, and leveraging appropriate testing tools and technologies. Additionally, efficient testing conventions enable teams to adapt to evolving project requirements and allocate resources effectively to achieve project objectives within stipulated timelines.
By adhering to these general guidelines, your organization can establish a robust framework for testing conventions that promotes consistency, clarity, and efficiency across all testing activities. These principles serve as guiding principles for developing specific testing conventions tailored to the unique needs and requirements of your projects and teams.
4. Test Case Conventions
Checklists serve as invaluable tools for ensuring consistency, completeness, and accuracy in the testing process. By adhering to established checklist conventions, teams can streamline their testing efforts, minimize errors, and improve the overall quality of software products. Below are the key components of checklist conventions:
4.1 Format:
Checklists should follow a standardized format to facilitate easy reference and usage. Typically, this format includes a list of items to be checked, along with checkboxes or indicators to mark the completion status of each item. Consistency in the format enables testers to quickly navigate and track the progress of testing activities.
4.2 Naming Conventions:
Checklists should be named descriptively, reflecting the purpose or scope of the testing activity. Clear and concise names help testers understand the objectives of the checklist and its relevance to the overall testing effort. Use a consistent naming convention across all checklists to maintain clarity and organization.
4.3 Structure:
Each checklist should follow a structured layout that guides testers through the verification process. Group related items logically to facilitate efficient execution and ensure comprehensive coverage. Provide clear instructions or guidance for each item to help testers understand what is expected and how to proceed.
4.4 Documentation:
Thorough documentation is essential for checklists to provide meaningful guidance to testers and stakeholders. Include detailed descriptions or explanations for each item to clarify its significance and relevance. Additionally, document any dependencies, prerequisites, or constraints that may impact the execution of the checklist. Clear documentation promotes consistency in execution and helps avoid misunderstandings or oversights.
By adhering to these checklist conventions, teams can enhance the effectiveness and efficiency of their testing processes. Well-structured, well-documented checklists enable testers to systematically verify the functionality, performance, and usability of software products, ultimately leading to improved quality and customer satisfaction.
5. Credential in All environment
Password: Admin@1234
6. Stripe Test Credential
Password: Lx8QaVKx6Ae63ce
Contact Rabab Khan (QA Engineer) for code
7. Repeat Process of Subscription Based Order
1. Go to MongoDB compass
c. {_id: ObjectId('_id')}
d. Click on find
e. Make next payment date as same as last payment date and increase 5 min time of next payment date.
f. Go to postman
Order > Create Recurring order> Run
g. Go to application. See order page. Order is repeated.
8. Info to setup custom SMTP
SMTP Password: qikqzjrpxrmcderx
SMTP Port: 465
Sent a Test Mail from Email Template. If mail is successfully sent, than it means SMTP Setup is successful, otherwise it has fault.
9. Process of Adding Custom Domain
10. Paypal Test Credential
Email: sb-4s6sr29130236@business.example.com
Password: SA7@eiwP
Email: sb-i2x2i30479158@business.example.com
Password: Ii|j)N0:
Card Number: 4032 0337 9408 4025
Expire Date: 06/2026
CVV: 606
Street address: 1600 Amphitheatre Parkway
city: Mountain View
state: California
zip: 94043
phone: (601) 952-1325
11. Cloudflare
chatgptplus777@gmail.com
CloudFl@re777
12. API Documentation from Codebase
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.