Scribd
Upload
5 views

Testing Manual and API

The document outlines key features and examples of test management and bug management tools, including their functionalities. It describes the Agile phases and various types of manual testing, along with the defect life cycle and testing methodologies. Additionally, it provides information on authentication methods in Postman, HTTP headers, and steps for performing manual testing.

Uploaded by

ayushgmail
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
5 views

Testing Manual and API

The document outlines key features and examples of test management and bug management tools, including their functionalities. It describes the Agile phases and various types of manual testing, along with the defect life cycle and testing methodologies. Additionally, it provides information on authentication methods in Postman, HTTP headers, and steps for performing manual testing.

Uploaded by

ayushgmail
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 3

Test Management Tools:

Key Features:
Test case creation and management.
Test execution tracking.
Test planning and scheduling.
Reporting and analysis of test results.
Integration with bug tracking tools.
Example tools: TestRail, PractiTest, qTest, Qase

Bug Management Tools:

Key Features:
Bug reporting and categorization.
Bug prioritization and assignment.
Tracking bug status and resolution.
Communication and collaboration among team members.
Reporting and analysis of bug trends.
Example tools: Jira, Bugzilla, BugHerd, Asana

RTM - Requirement Traceability Matrix,


Forward traceability : Tracks requirements from their origin throughout the project
lifecycle.
Backward traceability : Tracks the relationship between test cases and the
requirements that they test.
Bidirectional traceability: Tracks requirements from their origin and also tracks
the relationship between test cases and the requirements that they
test.

DSM - Daily Scrum call, Standup meeting.


Sprint Retrospective - A sprint retrospective aims to determine what went well and
where you had problems and identify areas where you can improve.

sprint planning - a meeting where a team discusses and plans the work they will do
during a sprint.
daily standups - daily meeting to discuss progress and identify blockers
sprint reviews - The Sprint Review is a working meeting where the Scrum Team
presents their completed work to stakeholders and asks for feedback.
sprint retrospective meetings - Scrum team events held after each sprint to inspect
and improve processes, identify areas for improvement, and plan for future sprints.

Agile Phases (Broader Agile process covering the entire project lifecycle.)
1. Inception Phase - Define vision, goals, and feasibility, stakeholders and high-
level requirements.
2. Iteration / Planning Phase - Break project into sprints. Prioritize and refine
backlog items,Assign tasks and estimate effort.
3. Development & Execution Phase - Sprints run iteratively, Continuous development,
testing, and integration., Adjustments based on feedback.
4. Release Phase - Deliver a potentially shippable product increment, Conduct user
testing and validation, Deploy the product.
5. Maintenance & Support Phase - Fix bugs, optimize performance, and add minor
enhancements, Continue support based on user feedback.

Definition of Manual Testing: Manual testing is a testing approach where testers


manually interact with software/app to check its quality without the help of
automated testing tools or test scripts.

Types of Manual Testing:


1. Functional Testing: Verifies that the software functions as described in the
requirements.
2. Non-Functional Testing: Evaluates aspects like performance, security, usability,
and reliability.
3. Black Box Testing: Testing without knowledge of the internal structure or code.
4.White Box Testing: Testing with knowledge of the internal structure and code.

Functions of Bugzilla as a Defect Management Tool:


1. Bug Tracking & Reporting
2. Workflow Management.(New → Assigned → Resolved → Verified → Closed)
3. Search & Filtering.
4. Bug Assignment & Notification.
5. Integration with Other Tools.
6. Reporting & Metrics.
7. Access Control & Security.
8. Customization & Scalability.

Function of Bug Management Tool:


1. Bug Tracking & Reporting
2. Customizable Workflow & Bug Lifecycle.
3. Bug Assignment & Notifications.
4. Integration with CI/CD & Version Control.
5. Advanced Search & Queries.
6. Reporting & Analytics.
7. Role-Based Access Control (RBAC).
8. Test Management Integration.

Informational responses (100 – 199)


Successful responses (200 – 299)
Redirection messages (300 – 399)
Client error responses (400 – 499)
Server error responses (500 – 599)

Authentication Ways in Postman:


1. No Auth
2. Basic Auth. - basic username, password
3. Bearer Token. - providing token(jwt,csrf)
4. JWT Bearer. - providing jwt bearer token.
5. Digest Auth - Similar to basic auth but more secure.
6. OAuth 1.0 - old auth mainly used for api requiring user auth and authorization.
7. OAuth 2.0 - used access token to authenticate APIs.
8. Hawk Authentication. - security protocol similar to oauth but simpler.
9. NTLM Authentication. -MS Authentication protocol used in win environment.

HTTP Headers - Key value pairs that are sent along with http request and responses.
1. Accept - defines the media type client able to accept.
2. User Agent - Identifies the web browser or client
3. Authorization - send client credential.
4. Content - Type - Media Type of the content in the request body.
5. Cookie - send previously stored cookie back to server.
6. Content - length - Specifies the size if response in bytes.

Defect Life Cycle:


1. New.
2. Assigned.
3. Open.
4. Fixed.
5. Retested.
6. Closed.
7. Reopened.
8. Deferred.

Sanity Testing: It is performed to check whether the new functionality/bug has been
fixed.
Smoke testing: It is performed to make sure the critical functionality of the
system is working completely.

Common approaches to API Testing are,


1. Contract Testing
2. Unit Testing
3. End to End Testing
4. Load Testing.

- Regression Testing: Involves manually retesting Software after changes are made.
- Exploratory Testing: Manual Testing Technique that relies on human exploration
and judgement.
- Black Box Testing - Manual Testing technique that relies on testing software
without relying on internal structure.

Manual Testing Tools:


1. BrowserStack live.
2. BrowserStack App live..
3. TestRail.
4. Jira.
5.Zephyr.
6.qTest.
7.Bugzilla.

Steps to perform Manual Testing:


1. Analyze Requirements from SRS.
2. Create a Test Plan.
3. Write Test case that covers all the requirements defined in document.
4. Review.
5. Execute and detect bugs.
6. Report or reverify.

Stages of Manual Testing:


1. Unit Testing - verification of individual component.
2. Integration Testing.
3. System Testing.-Testing all integrated modules of the software as a whole.
4. UI Testing. (GUI testing).

You might also like