Tuesday, May 19, 2015

Difference between Manual and Automation?

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.

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.

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
## Version & release number
##  Problem Summary / Short Description / Synopsis
## Steps to reproduce (Detailed Description)
## Screen shot of defect
## Severity (Critical, Serious, Minor, Suggestion)
## Priority (High, Medium, Low)
## Environment (Software and/or hardware configuration)
## Reported by
##  Assigned to
## 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 

==> 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

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 TuesdayThursday 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.

iii) Enter valid user ID & wrong 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.




Thursday, May 7, 2015

: BASIC DOS COMMAND:



: BASIC DOS COMMAND:
MD
To make a new directory
DIR
To list directory/File
RMDIR
To Remove/delete directory RMDIR [drive:]path
COPY
To Copy (File location than path to copy)  Example:
    C:\LAB1\QTP> COPY TEST.DOC C:\LAB2
RENAME (REN)
To rename file
NOTEPAD
To open notepad
CD
To change directory
DELETE (DEL)
To Delete file
FIND
To Find
CD..
To bring you 1 folder back
F:
To go others drive, like F:  (F: & hit enter)
                                     : SHORTCURT COMMAND IN DOS:
MSTSC
Remote desktop connection
REGEDIT
How to open registry file
TASKMGR
To open task manager
SYSDEM.CPL
To open system properties
NCPA.CPL
To open network properties
SERVICES.MSC
To open services
C:\>SYSTEMINFO | FIND "Host Name:"
Host Name:                 POLASH-PC
C:\>SYSTEMINFO | FIND "Total Physical Memory:"
Total Physical Memory:     6,020 MB

Wednesday, May 6, 2015

Software Development Life Cycle (SDLC)





what is a bug life cycle:-


Important Keyboard Short Cut In Windows 7


Abbreviation the following Computer Terminology:



CPU: Central Processing Unit

RAM: Random Access Memory 

USB: Universal Serial Bus 

UNC: Uniform Naming Convention 

BIOS: Basic Input Output System 

POST: Power On Self-Test 

CMOS:   Complementary Metal-Oxide Semiconductor 

SCSI:      Small Computer System Interface 

PCI:  Peripheral Component Interconnect 

RAID:     Redundant Array of Independent Disks 

IDE: Integrated Drive Electronics 

SAN:       Storage Area Networks 

CNSS:     Computer network security system.

What are the common solutions in software development process?



The common solutions in software development process are:
Ø  Solid requirement
Ø  Realistic schedule
Ø  Sufficient testing
Ø  Sufficient tools
Ø  Good communication

What are the common problems in software development process?


There are some problem in software development process, most of them are:

Ø  Poor requirement
Ø  continuously changing RM
Ø  schedule problem
Ø  insufficient tools
Ø  Miscommunication

What is your day to day activity as a tester?


Well, it is actually depends on what kind of methodology you are using. And what kind of environment you are working?

Generally day to day activities are:
1)      Check the email and replay back if needed
2)      Check calendar for make sure any meeting scheduled or not
3)      Join the Daily Stand-Up Meeting. Where we basically ask 3 question each other:
Ø  What you have done so far?
Ø  What you want to do today?
Ø  Any blockers?

4)      Preparing test scenarios, writing the test cases, prepare test data and executing the test cases.

5)      If I found any bug then log to my lead.

What Is the Uses Of SQL?



  • SQL can create new tables in a database
  • SQL can insert records in a database
  • SQL can update records in a database
  • SQL can delete records from a database
  • SQL can create stored procedures in a database
  • SQL can retrieve data from a database
  • SQL can create views in a database
  • SQL can set permissions on tables, procedures, and views

What is SQL and why tester need SQL?




What is SQL and why tester need SQL?


SQL stands for Structured Query Language. SQL is an ANSI (American National Standards Institute) standard computer language for accessing and manipulating database systems. SQL statements are used to retrieve and update data in a database. SQL works with database programs like MS Access, DB2, Informix, MS SQL Server, Oracle, Sybase, etc.

Why tester need SQL:

Yes, a tester needs to know SQL. When we do the back-end testing, we need to write SQL queries to retrieve the data from the database and compare this data to the one with reports or output.

Another scenario is, if something goes wrong in the application, for example, if there is an error, then we might have to write SQL queries to retrieve the data from the database and check what went wrong. Let’s say, we need to check in the Error Log table what went wrong. To check this, we query to the database, go to Error Log table and find out that happened. In the Error Log table, there are many records, so which one is your error then? To find out which one is yours, we need to write SQL queries. Example, you logged in to the application with User ID=devin99 and password=sn992jj. Now, to retrieve your record, you can write a query something like this: select * from Error_Log where userID=devin99; this query will retrieve your record only so that you can see what happened.

Best Site To Learn SQL

http://www.w3schools.com/

Tuesday, May 5, 2015




What is the role & responsibility for a QA tester or what is the manual testing process  


Basically a tester has lot of role & responsibility in a testing life cycle, most of them are:

Ø  Study FRD (functional requirement document)
Ø  create LOE
Ø  prepare test plan
Ø  prepare test scenario
Ø  create  test cases, prepare test data, execute test cases
Ø  mapping test cases to the requirement cases
Ø  manage defect, reports defect
Ø  communicate with Test Lead, Test manager, Developer
Ø  successfully collaborate with scrum master & team members
Ø  comfortable with using SQL





What is the quality for a good tester?


Some basic thing for a quality tester is:
Ø  Excellent communication skills.
Ø  Out of box thinkers.
Ø  Quick learner.
Ø  Good thinking & analyzing skill
Ø  Think from customer view.
Ø  A team player.

OUR GOAL !!