qualitytesting-blog
qualitytesting-blog
QualityTesting
100 posts
QTP Book for learning Software Testing and QTP (Quick Test Professional) Automation. This Online QTP Book Site includes everything from QTP Basics to QTP best practices. http://qtpbook.com/
Don't wanna be here? Send us removal request.
qualitytesting-blog · 12 years ago
Photo
Tumblr media
Focusing on selling Software Testing eBook
You can buy this eBook from here. I have announced a Offer price for boosting the eBook Sales. This Offer will be available for few days only. I am planning to start running PPC campaigns for promoting this eBook  in few days. I may increase the eBook price to cover the ads charges. So, if you want to utilize this Offer price, buy this eBook today itself. And, still you can freely read this Book content from  QTPbook.com
6 notes · View notes
qualitytesting-blog · 12 years ago
Link
What is Recording Modes?
Quick Test supports three different types of recording modes such as Normal mode, Analog mode and Low Level Recording mode.
Normal- QuickTest’s normal recording mode records the objects in your application and the operations performed on them. This mode is the default and takes full advantage of QuickTest’s test object model, recognizing the objects in your application regardless of their location on the screen.
Analog – This mode records and tracks every movement of the mouse.
Low level -records at the object level and records all run-time objects as Window or WinObject test objects.
Low Level Recording supports the following methods for each test object.
More to know about WinObject test object
2 notes · View notes
qualitytesting-blog · 12 years ago
Text
QTP trial version installation
Learning QTP (Quick Test professional) will become easy if we practice some simple tutorials with QTP.
HP is providing free trail offer for Quick Test Professional.
Follow below steps to have a QTP set up.
First do keyword search for “quick test professional” in HP website
You can see the download link under “trail versions” in the search result.
Once after downloading it you can easily install it just by clicking the setup icon. You will need maintenance number while doing installation. You can contact the HP to provide Maintenance number for you.
This Trail version will be valid for 14 days which is enough to learn QTP
0 notes
qualitytesting-blog · 12 years ago
Video
Funny Moment of Barack Obama Family. (by Rajamanickam Antonimuthu)
2 notes · View notes
qualitytesting-blog · 12 years ago
Link
Discussion about Various Skills (Domain knowledge, Communication Skills, Technical skills, etc) required for Software Testers
Software Testers need to have below skills.
Testing skill
Domain knowledge
Technical skills
Communication skill
Automation skill
programming skill
If I missed to mention any other important skills, you can say it thro’ the comments.
1 note · View note
qualitytesting-blog · 12 years ago
Photo
Tumblr media
10 FACTS ABOUT YOU
0 notes
qualitytesting-blog · 12 years ago
Quote
Hi Welcome to QTPBook.com.
Welcome from QTPBook.com.
0 notes
qualitytesting-blog · 12 years ago
Link
Discussion about Various Skills (Domain knowledge, Communication Skills, Technical skills, etc) required for Software Testers
Software Testers need to have below skills.
Testing skill
Domain knowledge
Technical skills
Communication skill
Automation skill
programming skill
1 note · View note
qualitytesting-blog · 12 years ago
Text
How to write Test Cases?
What is  Test Case ?
Test case is “Documentation specifying inputs, predicted results, and a set of execution conditions for a test item.” The  purpose of Test Case  is to divide the software function into small units of function that is testable with input, and producing result that is measurable.
i-e  A test case is a feature/function description that should be executed with a range of input, given certain preconditions, and the outcome measured against expected result.
These are the  fields commonly present in the Test Cases :
Test case id
Test Case Description
Procedure / Test Steps
Test data
Expected result
Actual result
Status ( Pass/ Fail)
Comments
Test cases should be simple and easy to understand for Developers.
Test Case ID :
This ID should be Unique throughout the Testing Application and not to change at any moment.
Test Case Description:
Explain the function under test. Clearly state exactly what attribute is under test and under what condition.
Prerequisites- Every test needs to follow a sequence of actions, which lead to the function under test. It could be a certain page that a user needs to be on, or certain data that should be in the system . For example  registration step should be completed before start testing login.
Procedure/Steps:
Sequence of steps to execute the specific function.
Test data:
Specify the data used for a particular test or if it is a lot of data, mention the path of a file where this data is stored.
Expected Result:
Clearly specify the expected outcome in terms of the page/ screen that should appear after the test, changes that should happen to other pages, and if possible, changes that should happen to the database..
Actual Result :
State the actual result of the function execution. Especially in case the test case fails, the information under ‘actual result’ will be very useful to the developer to analyse the cause of the defect.
Comments:
In this section you can add your reviews, suggestions and ideas to developers for the bug how we fix that.  Especially this section made to communicate with developers.
Read more http://qtpbook.com/2013/05/14/how-to-write-test-cases/
2 notes · View notes
qualitytesting-blog · 12 years ago
Text
Software Testing Questions and Answers
Give the answers for the queations.
1) The approach/document used to make sure all the requirements are covered when writing test cases a) Test Matrix b) Checklist c) Test bed d) Traceability Matrix
2) Executing the same test case by giving the number of inputs on same build called as a) Regression Testing b) ReTesting c) Ad hoc Testing d) Sanity Testing
3) Control Charts is a statistical technique to assess, monitor, and maintain the stability of a process. a) True b) False
4) To check whether we are developing the right product according to the customer requirements are not. It is a static process a) Validation b) Verification c) Quality Assurance d) Quality Control
5) To check whether we have developed the product according to the customer requirements r not. It is a Dynamic process. a) Validation b) Verification c) Quality Assurance d) Quality Control
6) Staff development plan describes how the skills and experience of the project team members will be developed. a) True b) False
7) It is a set of levels that defines a testing maturity hierarchy a) TIM (Testing Improving Model) b) TMM (Testing Maturity Model) c) TQM(Total Quality Management)
8) A Non-Functional Software testing done to check if the user interface is easy to use and understand a) Usability Testing b) Security Testing c) Unit testing d) Block Box Testing
9) The review and approved document (i.e. Test plan, System Requirement Specification’s) is called as a) Delivery Document b) Baseline Document c) Checklist
10) What are the Testing Levels? a) Unit Testing b) Integration Testing c) System Testing and Acceptance Testing. d) All the above
11) Cost of quality = Prevention Cost + Appraisal cost + Failure cost a) True b) False
12) A useful tool to visualize, clarify, link, identify, and classify possible cause of a problem. This is also called as “fishbone diagram” what is this? a) Pareto Analysis b) Cause-and-Effect Diagram
13) It measures the quality of processes used to create a quality product. It is a system of management activities, It is a preventive process, It applies for entire life cycle & Deals with Process. a) Validation b) Verification c) Quality Assurance d) Quality Control
14) Variance from product specifications is called? a) Report b) Requirement c) Defect
15) Verification is a) Process based b) Product based
16) White box testing is not called as___________ a) Glass box testing b) Closed box testing c) Open box testing d) Clear box testing
17) Name the events that will be analyzed, Count the named incidents, Rank the count by frequency using a bar chart & Validate reasonableness of the analysis is called as a) Pareto Analysis b) Cause and Effect Diagram c) SWOT Analysis d) Pie Charts
18) Retesting of a single program or component after a change has been made? a) Full Regression Testing b) Unit Regression c) Regional Regression d) Retesting
19) Requirement and Analysis, Design, Development or Coding, Testing and Maintenance is called as Software Development Life Cycle (SDLC ) a) True b) False
20) The testing which is done by going thro’ the code is known as, a) Unit Testing b) Blackbox testing c) White box Testing d) Regression testing
21) Configuration Management Plan describes the Configuration Management procedures and structures to be used. a) True b) False
22)This type of testing method attempts to find incorrect or missing functions, errors in data structures or external database access, interface errors, Performance errors and initialization and Termination errors. It is called as a) White Box Testing b) Grey Box Testing c) Black Box Testing d) Open Box Testing
23) Phase Definition. It will come under a) CMM Level 1 b) CMM Level 2 c) None
24) Software testing which is done without planning and Documentation is known as a) adHoc Testing b) Unit Testing c) Regression testing d) Functional testing.
25) Acceptance testing is known as a) Beta Testing b) Greybox testing c) Test Automation d) White box testing
26) Retesting the entire application after a change has been made called as? a) Full Regression Testing b) Unit Regression c) Regional Regression d) Retesting
27) Boundary value analysis belongs to which testing method? a) Black Box testing b) White Box testing
28) It measures the quality of a product It is a specific part of the QA procedure, It is a corrective process, It applies for particular product & Deals with the product. a) Validation b) Verification c) Quality Assurance d) Quality Control
29) What are the Types of Integration Testing? a) Big Bang Testing b) Bottom Up Testing c) Top Down Testing d) All the above
30) Product Risk affects The quality or performance of the software. a) True b) False
Answers for above 30 questions.
1 note · View note
qualitytesting-blog · 12 years ago
Photo
Tumblr media
Are you a Fresh Graduate looking for Experience/Entry? Don’t wait for anyone’s Permission.
  We can see many Fresh Graduates worrying about gaining Experience for getting job especially Job in IT Company.
Their worry seems to be valid at first look; But actually it is not, if we think about it deeply.Most of the people used to say “Getting entry into IT job is difficult”. Their reason is “You will need experience for getting Job, and you will get experience only when you get a Job“. It will be cyclic and it is difficult to break this cycle.
But, you can easily break this cycle by getting experience in Software Development even without getting any job. i-e You need not get permission from anyone to get job experience.
(I am not talking about wrong approaches such as putting fake experience or paying for getting experience. Actually these wrong approaches will do more harm than good for you.)
You can start a new open-source project or you can join with any existing open source projects. If you are not comfortable with programming, you can do Software Testing or Documentation. Open Source projects need lot of people for doing QA and Documentation. You can get the open source projects from sourceforge.net, codeplex.com andcode.google.com.
You can start your own website for learning purpose. You can start with simple html/css/javascript and then improve your site step by step with lot of other features. Many large sites (e.g imdb) are started like this only.
Learn using API of Social networking sites. e.g Twitter client and Facebooks apps. Develop your own application and try to spread it thro’ the social networking site.
You can develop app if you have Smart Phone. Getting your app into the iPhone AppStore or Google Play Store (Android marketplace) will increase the possibility of getting job.
You can bid for a small job in Freelance websites, if you quote the price very less you will get an opportunity for getting the project. Even if you didn’t get the project just get the spec and start doing it.
You can approach any local business and help them to reduce their work by implementing small software projects for them.
Use your free time to come up with ideas. Whether it’s an idea for a marketing campaign, new revenue stream, cost savings, etc, the candidates who show up at an interview with ideas demonstrate that they are passionate, knowledgeable, and excited about the opportunity. These job seekers always stand out from the crowd.
If you do a great job, even if it’s for a temporary job, whoever hired you is more likely to recommend you for a permanent position.
You will get handful of experience if you follow above steps, and adding these experience in your resume will get you job in IT Company Soon.
1 note · View note
qualitytesting-blog · 12 years ago
Link
Easily search lot of QTP and other QA related job openings from single Search box.
We have launched a Job Search Engine for allowing the users to search latest job openings easily without requiring them to use lot of job sites and employers career pages.
Though this Search Engine can be used for searching any kind jobs, we have specifically optimized it for effectively searching QTP (Quick Test professional) and any other QA (Quality Assurance) related job openings.
You can start using it at http://autoresumepost.com/jobsearch.php and you can read about this job search engine here.
1 note · View note
qualitytesting-blog · 12 years ago
Text
eBook for learning Software Testing And QTP (HP Quick Test Professional) Automation
This eBook will be useful for learning Software Testing and it covers from Basics to Best practices about learning and using QTP (Quick Test Professional) which is more popular among Software Test Automation Tools.
This eBook Covers below topics.
Importance of Software Testing
Basics of Quality Assurance (QA) in Software Development
Explains below Terms used in Software Testing.
Software Development Life Cycle (SDLC)
Functional & Non-functional Testing
Testing methods (whitebox, blackbox and Greybox)
Testing levels (Unit Testing, Integration Testing, System testing, Regression testing, Alpha Testing, Beta testing)
Testing Artifacts (Test plan, Traceability matrix, Test suite, Test case)
Software Test life cycle
Bug Tracking
Writing Good Test Cases and Finding Bugs effectively
Tips and Tricks for doing AdHoc Testing
Best practices in Software Testing
Importance of Software Test Automation using tools such as QTP
Need of Domain Knowledge for Software Testers
Software Test Automation tool evaluation
The need for having development/programming knowledge for Software Testers
Software Testing Questions and Answers
Introduction to QTP
How to Learn QTP?
Understanding Object Repository
Different Types of Object Repositories- Local and Shared
Associating Repositories
Understanding Action Iteration and Test Iteration
Required Steps/Processes in QTP Automation
Best Practices in QTP Automation
Scheduling QTP Script Execution
Basics of vbscript
Links Useful for learning QTP
KeyWord Driven Testing and Framework in QTP
Descriptive Programming in QTP – Advantages and Disadvantages
Tips for doing effective QTP script Development
Recording Modes – Normal, Analog and Low level recording
Run Mode- Update Run and Fast Run
CheckPoints
Data Tables – Global and Local Sheets
QTP Result Window
Recovery Scenario
Synchronization Points
Automation Object Model (AOM)
Handling Passwords in QTP Scripts
Managing Object Repositories in QTP
Object Spy in QTP
QTP methods and script for reading object properties
Some Thoughts on QTP Interview
QTP trial version installation.
Wish list for the QTP future release
QTP Questions and Answers
More Details http://qtpbook.com/ebook-for-learning-software-testing-and-qtp-hp-quick-test-professional-automation/
0 notes
qualitytesting-blog · 12 years ago
Photo
Tumblr media
Facebook Acquires Speech-Recognition startup Mobile Technologies
Facebook announced that it has acquired Mobile Technologies,a leading speech recognition company. 
  Facebook product manager Tom Stocky announced the acquisition via Facebook.He said, “I’m excited to announce that we’ve agreed to acquire Mobile Technologies, a company with an amazing team that’s behind some of the world’s leading speech recognition and machine translation technology.
Mobile Technologies said on its website, “Facebook, with its mission to make the world more open and connected, provides the perfect platform to apply our technology at a truly global scale.
Once the deal has closed many team members from MobileTechnologies will be joining the Facebook at their headquarters in Menlo Park, California.
0 notes
qualitytesting-blog · 12 years ago
Link
Today(14 August 2013), Pakistan celebrating 66th Independence Day. Google shows Pakistan Independence Day 2013 with an amazing Google Doodle.
0 notes
qualitytesting-blog · 12 years ago
Link
Facebook chief operating officer Sheryl Sandberg has sold off $91 million worth of stock this week, according to a filing with the Securities and Exchange Commission.
Sandberg, who has periodically sold some of her holdings since Facebook’s May 2012 IPO, on Wednesday cashed in a total of 2.37 million shares at prices ranging from $37.79 to $38.78.
Over the past few weeks, Facebook’s stock price steadily rose and finally hit its IPO price of $38 a share on July 31.
The social network brought in $1.813 billion in revenue last quarter, which is 53 percent year over year.
RtoZ.org
0 notes
qualitytesting-blog · 12 years ago
Text
Software Development Life Cycle (SDLC)
SDLC involves different phases such as Initial/Planning phase, Requirement analysis phase, Design phase, Coding phase, Testing phase, Delivery and Maintenance phase.
All these phases can be followed one by one linearly as Waterfall model or they can be followed as V-modelwhich expects doing Testing activities in parallel with development activities.
Initial Phase involves gathering requirements by interacting with the Customer. Normally Business Analyst will do this and will prepare a requirement document.
Here Customer is the internal marketing team in case of product development. Otherwise Customer is the person who is paying for doing the project.
Requirement analysis phase involves doing detailed study of the customer requirements and judging possibilities and scope of the requirements. And it involves tentative planning and technology & resource selection.
SRS (System Requirement Specification) will be created in this phase.
Design phase involves dividing the whole project into modules and sub-modules by doing High level Designing (H.L.D) and   Low level Designing   (L.L.D).
Coding Phase involves creating source code or program by the programmers by referring the design document.  Coding standards with proper comments should be followed.
Testing Phase involves getting clarification for the unclear requirements and then writing test cases by Testing Team based on the requirements. And, the testing team will execute the test cases once the build is released and they will report the bugs found during the test case execution.
Delivery & Maintenance phase  involves installing the application in the customer place and providing the details such as release notes to the customer.
Maintenance or support Team will help the customers if they face any issue when using the application.
Software Testing – It is the process of verifying whether a software application or a software product meets thebusiness and technical requirements. i-e verifying whether the developed software application works as expected.
It will be done by comparing the Actual result against the Expected Result.
For example, if the requirement says “After entering valid username and password the user should be logged in to the website” software testing is nothing but just entering valid user name and password to verify whether the user got logged in to the website.
But, doing software testing is not so simple, lot of complex factors involved in doing testing. It needs lot ofthinking and brainstorming processes.
In this simple example, we should know below things.
In which environment we need to do the login testing?
What is valid username and password?
How to verify whether the user really logged into the website?
How long it will take to complete the login?
How the system should behave if the user enters invalid username or invalid password?
What will happen if the user already logged in?
How the system should behave if someone continuously try to login by giving invalid username and password?
Is it possible to reach the target page even without doing login?
How the system will behave if there is any network issue once after entering the username and password?
What will happen if two people try to login with same username and password simultaneously from two different machines?
How the system will behave if the user doesn’t use the website for longtime once after getting logged in?
Will the login process take same time even after Millions of users registered with the system?
What will happen if thousands of people try to do login at same time?
What message will be shown to the user if the database which stores the user details goes down?
 Will the system provide any other interface (e.g API, webservice) other than the standard UI for doing login?
How to help the user if he forgot the password?
Will the system allow the username in non-English also?
Most importantly, when we need to do this login testing?
What are the pre-requisites? (e.g user should be registered before testing login).
Is it necessary to do the testing in production environment also?
To whom should we report if the Testing fails? And, what are the details we need to provide? How we come to know once it got fixed? What we need to do once after it got fixed?
Is there any option (e.g Remember Me cookie, auto-complete) for making the login easy? Will these options break the login system in any way?
 Whether anyone (e.g hacker) can access the password while doing login?
Whether the password is not readable to the developers of the system so as to avoid any misuse? (e.g password encryption before storing it in Database)
If we need to do this testing multiple times in many environments, is there any easy way to do the testing? (e.g using scripts and automation tools such as QTP)
Will it work correctly in different user interfaces (e.g Different browsers such as Internet Explorer, FireFox, Safari, Chrome), and in different settings (e.g javascript disabled)?
Is the code is written well enough so that future enhancements can be made easily?
Who has to do this testing? Whether the developer of the system can do the testing also?
So, it is important to have clear understanding of testing approaches before start doing any testing.
Functional & Non-functional Testing
0 notes