MANUAL TESTING:
Manual testing is time consuming, not robust, uses human resources, harder to repeat a test and costly.
AUTOMATED TESTING:
Automated testing is faster, robust, easily repeatable, Reusable and cost efficient. Therefore, Company should use automated testing for save their time, money and human resources.
Tuesday, May 19, 2015
Difference between Manual and Automation?
What is automation?
Automation is a process that executes manual test cases into automation script and Execute that same Functionality without user interact.
Example: Lets say we have test case for login to an application. For perform this test manually we need open browser, we need to navigate to the application URL, then insert valid credentials to the WEBEDIT and finally we need to click on login button.
Instead of doing manually we can easily automate this test case and run it for multiple number of users without any human interact.
Example: Lets say we have test case for login to an application. For perform this test manually we need open browser, we need to navigate to the application URL, then insert valid credentials to the WEBEDIT and finally we need to click on login button.
Instead of doing manually we can easily automate this test case and run it for multiple number of users without any human interact.
Design Steps In Quality Center (QC)
Monday, May 18, 2015
New Defect Report Page In Quality Center (QC):
What are Bug Report components? or What fields do you fill out in a Bug Report?
## ID number: Unique number given to the report
## Date
## Application / Module being tested
## Application / Module being tested
## Version & release number
## Problem Summary / Short Description / Synopsis
## Steps to reproduce (Detailed Description)
## Problem Summary / Short Description / Synopsis
## Steps to reproduce (Detailed Description)
## Screen shot of defect
## Severity (Critical, Serious, Minor, Suggestion)
## Severity (Critical, Serious, Minor, Suggestion)
## Priority (High, Medium, Low)
## Environment (Software and/or hardware configuration)
## Reported by
## Reported by
## Assigned to
## Status (Open, Pending, Fixed, Closed, cannot reproduce, etc.)
## Comments/ Notes
## Status (Open, Pending, Fixed, Closed, cannot reproduce, etc.)
## Comments/ Notes
What is Business Requirements Document (BRD)?
BRD is written by the Business Analysts. It details the business solution for a project including the documentation of customer needs and expectations.
The most common objectives of the BRD are:
==> To gain agreement with stakeholders
==> To provide a foundation to communicate to a technology service provider what the solution needs to do to satisfy the customer's and business’ needs
The most common objectives of the BRD are:
==> To gain agreement with stakeholders
==> To provide a foundation to communicate to a technology service provider what the solution needs to do to satisfy the customer's and business’ needs
==> To provide input into the next phase for this project
==> To describe what not how the customer/business needs will be met by the solution
==> To describe what not how the customer/business needs will be met by the solution
Sunday, May 17, 2015
What is a test cases and what is the purpose of a test cases?
Test Case:
A test case is a document that describes step by step process how to test the application.
Test case includes:
Test case ID, Step Name, Step Description, Test Data, Expected Output, Actual Output, Pass/Fail and comments.
The purposes of the test case are:
Ø To achieve the 100% RM coverage
Ø Reduce the defect in the application
Ø Verifying standards guideline
Ø Validating users need
Thursday, May 14, 2015
ITCloud Demo :-
We are excited to let you know that our orientation will be held on May 16, 2015 at 8:00 PM (EST).
Shortly we are going to provide DEMO joining URL to all attendees.
Also training session going to be start from May 19, 2015. Our regular online session will begin 8:00PM – 10:00PM (EST).
As you already know, this session will take place on every Tuesday, Thursday and Friday. Before the session begins, our admin will send you meeting links through email. If you have any concern, please feel free to call our admin at 954-861-9365.
Wednesday, May 13, 2015
What is a test scenario?
A test scenario is a functionality of the application that can be tested. Test scenario also called Test condition or Test possibility.
Example: scenario for the user login functionality:
Scenario for positive testing:
i) Enter valid user ID & password in the login window then click login. User able to login.
Scenario for negative testing:
i) Leave blank user ID & Password field, click login – Error message displays.
ii) Enter invalid user ID & wrong password, click login – Error message displays.
Example: scenario for the user login functionality:
Scenario for positive testing:
i) Enter valid user ID & password in the login window then click login. User able to login.
Scenario for negative testing:
i) Leave blank user ID & Password field, click login – Error message displays.
ii) Enter invalid user ID & wrong password, click login – Error message displays.
iii) Enter valid user ID & wrong password, click login, - Error message displays.
iv) Enter invalid ID & right password, click login - Error message displays.
iv) Enter invalid ID & right password, click login - Error message displays.
Saturday, May 9, 2015
DEMO CONFIRMATION:-
We are excited to let you know that our orientation will be held on May 16, 2015 at 8:00 PM (EST).
Also training session going to be start from May 19, 2015. Our regular online session will begin 8:00PM – 10:00PM (EST).
As you already know, this session will take place on every Tuesday, Thursday and Friday. Before the session begins, our admin will send you meeting links through email. If you have any concern, please feel free to call our admin at 954-861-9365.
Also training session going to be start from May 19, 2015. Our regular online session will begin 8:00PM – 10:00PM (EST).
As you already know, this session will take place on every Tuesday, Thursday and Friday. Before the session begins, our admin will send you meeting links through email. If you have any concern, please feel free to call our admin at 954-861-9365.
Subscribe to:
Posts (Atom)


