Quality

Test Plan Template :

noreply@blogger.com (Saurabh) — Thu, 21 Mar 2013 16:23:00 +0000

Test Plan Template:
(Name of the Product)

Prepared by:
(Names of Preparers)
(Date)

TABLE OF CONTENTS :
1.0 INTRODUCTION
2.0 OBJECTIVES AND TASKS
2.1 Objectives
2.2 Tasks
3.0 SCOPE
4.0 Testing Strategy
4.1 Alpha Testing (Unit Testing)
4.2 System and Integration Testing
4.3 Performance and Stress Testing
4.4 User Acceptance Testing
4.5 Batch Testing
4.6 Automated Regression Testing
5.0 Hardware Requirements
6.0 Environment Requirements
6.1 Main Frame
6.2 Workstation
7.0 Test Schedule
8.0 Control Procedures
9.0 Features to Be Tested
10.0 Features Not to Be Tested
11.0 Resources/Roles & Responsibilities
12.0 Schedules
13.0 Significantly Impacted Departments (SIDs)
14.0 Dependencies
16.0 Tools
17.0 Approvals

Latent Bug

noreply@blogger.com (Saurabh) — Tue, 28 Feb 2012 06:37:00 +0000

Latent Bug is a bug which is not identified in present version and can be able to identified in later versions. Also called as Golden Bug.

Gap Analysis

noreply@blogger.com (Saurabh) — Tue, 28 Feb 2012 05:57:00 +0000

The gap analysis process involves determining, documenting and approving the variance between business requirements and current capabilities.It is the comparison study of general expectation of performance in the industry and the level of performance at
which the company currently functions.

Gap analysis provides a foundation for measuring investment of time, money and human resources required to achieve a particular outcome (e.g. to turn the salary payment process from paper based to paperless with the use of a system).

Such analysis can be performed at the strategic or operational level of an organization.'Gap analysis' is a formal study of what a business is
doing currently and where it wants to go in the future. It can be conducted, in different perspectives, as follows:

Organization (e.g., human resources)
Business direction
Business processes
Information technology

Also

Banking and financial services organizations often ask this question, as they face the risk of missing or incompletely covered Business Requirements (BR) in Functional Specifications Documents (FSDs). This risk arises as business users may not always articulate their basic requirements under the misconception that development vendors know them already. However, that is not often the case because technology focused developers do not understand the nuances of banking like a domain specialist can.

Inconsistencies between Business Requirements and Functional Specifications result in critical requirement gaps later in the product life cycle. This often proves very costly for the client and the vendor, in terms of both monetary and reputation loss.

Defect Leakage

noreply@blogger.com (Saurabh) — Tue, 28 Feb 2012 05:38:00 +0000

Defect leakage occurs at the Customer or the End user side after the application delivery.After the release of the application to the client, if the end user gets any type of defects by using that application then it is called as Defect Leakage.This is also called as Bug Leakage.

Agile methodology over the Waterfall method

noreply@blogger.com (Saurabh) — Tue, 28 Feb 2012 05:02:00 +0000

1. Once a stage is completed in the Waterfall method, there is no going back, since most software designed and implemented under the waterfall method is hard to change according to time and user needs. The problem can only be fixed by going back and designing an entirely new system, a very costly and inefficient method. Whereas, Agile methods adapt to change, as at the end of each stage, the logical programme, designed to cope and adapt to new ideas from the outset, allows changes to be made easily. With Agile, changes can be made if necessary without getting the entire programme rewritten. This approach not only reduces overheads, it also helps in the upgrading of programmes.
2. Another Agile method advantage is one has a launchable product at the end of each tested stage. This ensures bugs are caught and eliminated in the development cycle, and the product is double tested again after the first bug elimination. This is not possible for the Waterfall method, since the product is tested only at the very end, which means any bugs found results in the entire programme having to be re-written.
3. Agile’s modular nature means employing better suited object-oriented designs and programmes, which means one always has a working model for timely release even when it does not always entirely match customer specifications. Whereas, there is only one main release in the waterfall method and any problems or delays mean highly dissatisfied customers.
4. Agile methods allow for specification changes as per end-user’s requirements, spelling customer satisfaction. As already mentioned, this is not possible when the waterfall method is employed, since any changes to be made means the project has to be started all over again.
5. However, both methods do allow for a sort of departmentalization e.g. in waterfall departmentalization is done at each stage. As for Agile, each coding module can be delegated to separate groups. This allows for several parts of the project to be done at the same time, though departmentalization is more effectively used in Agile methodologies.

Values of Agile Modeling

noreply@blogger.com (Saurabh) — Mon, 27 Feb 2012 14:32:00 +0000

The five values of Agile Modeling (AM) are:
1.Communication : Models promote communication between your team and your project stakeholders as well as between developers on your team.
2.Simplicity : It’s important that developers understand that models are critical for simplifying both software and the software process—it’s much easier to explore an idea, and improve upon it as your understanding increases, by drawing a diagram or two instead of writing tens or even hundreds of lines of code.
3.Feedback : Kent Beck says it best in Extreme Programming Explained: “Optimism is an occupational hazard of programming, feedback is the treatment.” By communicating your ideas through diagrams, you quickly gain feedback, enabling you to act on that advice.
4.Courage : Courage is important because you need to make important decisions and be able to change direction by either discarding or refactoring your work when some of your decisions prove inadequate.
5.Humility : The best developers have the humility to recognize that they don't know everything, that their fellow developers, their customers, and in fact all project stakeholders also have their own areas of expertise and have value to add to a project. An effective approach is to assume that everyone involved with your project has equal value and therefore should be treated with respect. Huet Landry suggests the concept of "Other Esteem", instead of "Self Esteem", where you treat the opinions of others as if they have more value than yours. With this approach your first reaction to another's idea will be most positive.

Difference Between Authorization And Authentication

noreply@blogger.com (Saurabh) — Mon, 27 Feb 2012 14:09:00 +0000

Authentication is the process to test whether the specific user is allowed to use or login to the application.

And

Authorization we test whether the specific user allowed to access some controls or features of the system/application/software.

Eg: In an office automation tool, every employee can login to the application, but only accounts manager can access accounts related features, only HR manager or executive can access company information

Severity And Priority

noreply@blogger.com (Saurabh) — Mon, 27 Feb 2012 13:55:00 +0000

Severity
1. The Severity status is used to explain how badly the deviation is affecting the build.
2. The Severity type is defined by the tester on the written test cases and functionality.

Ex : If an aaplication or a web page crashes when a remote link is clicked,in this case clicking the remote link by an user is rare but the impact of application crashing is severe,so the severity is high and priority is low.

Priority
1. The Priority status is set by the tester to the developer mentioning the time frame to fix a defect.If High priority is mentioned then the developer has to fix it at the earliest.
2. The priority status is set based on the customer requirements.

Ex : If the company name is misspelled in the home page of a website, then the priority is high and the severity is low to fix it

Quote 10

noreply@blogger.com (Saurabh) — Sun, 17 Jul 2011 18:11:00 +0000

“If you don’t care about quality, you can meet any other requirement.” – Gerald M. Weinberg

Quote 9

noreply@blogger.com (Saurabh) — Sun, 17 Jul 2011 18:08:00 +0000

“More than the act of testing, the act of designing tests is one of the best bug preventers known. The thinking that must be done to create a useful test can discover and eliminate bugs before they are coded – indeed, test-design thinking can discover and eliminate bugs at every stage in the creation of software, from conception to specification, to design, coding and the rest.” – Boris Beizer

Quote 8

noreply@blogger.com (Saurabh) — Sun, 17 Jul 2011 18:06:00 +0000

“Quality is never an accident; it is always the result of intelligent effort.” – John Ruskin

Quote 7

noreply@blogger.com (Saurabh) — Sun, 17 Jul 2011 18:05:00 +0000

"It's more about good enough than it is about right or wrong." (James Bach)

Quote 6

noreply@blogger.com (Saurabh) — Sun, 17 Jul 2011 18:02:00 +0000

“Irreproducible bugs become highly reproducible right after delivery to the customer.”

Quote 5

noreply@blogger.com (Saurabh) — Sun, 17 Jul 2011 17:59:00 +0000

"Before software can be reusable it first has to be usable.” – Ralph Johnson.

Accessibility Testing

noreply@blogger.com (Saurabh) — Sun, 17 Jul 2011 06:28:00 +0000

Testing that determines if software will be usable by people with disabilities.

It is also called as ADA testing or 508 complaiance testing.(American disabilities act). Testing the application with respect to physically challenged persons point of view is called accessibility tesing..

Such as blindness, low or restricted vision, or color blindness. User with visual impairments uses assistive technology software that reads content loud. User with weak vision can also make text larger with browser setting or magnificent setting of operating system.

To know more plz visit Accessibility more

OR

To know more plz visit Testing for Accessibility MSDN

Quote 4

noreply@blogger.com (Saurabh) — Sun, 09 Jan 2011 13:55:00 +0000

Priorities tests so that whenever you stop testing you have done the best testing in the time available.

The 'Oracle Assumption'

noreply@blogger.com (Saurabh) — Sun, 09 Jan 2011 13:48:00 +0000

For most systems it is possible to predict the expected results for any test case but there are a few systems where this is not the case.

For example, systems that predict situations or perform long and complex calculations that cannot practically be performed manually.

The Oracle Assumption is the name given to the assumption that it is possible to predict the expected results.

Quote 3

noreply@blogger.com (Saurabh) — Sun, 09 Jan 2011 13:45:00 +0000

Testing is looking for something you don't really want to find.

Quote 2

noreply@blogger.com (Saurabh) — Sun, 09 Jan 2011 13:44:00 +0000

The best way to build confidence is to try and destroy it.

Quote 1

noreply@blogger.com (Saurabh) — Sun, 09 Jan 2011 13:37:00 +0000

You cannot have justified confidence in the quality of the software unless you have confidence in the quality of the Testing.

Testing Completion Criteria

noreply@blogger.com (Saurabh) — Sun, 09 Jan 2011 13:14:00 +0000

Testing Completion Criteria includes following things -
1. 100% Statement coverage,
2. 100% Requirement coverage,
3. All screens / dialogue boxes / error messages seen,
4. 100% of test cases have been run,
5. 100% of high severity fault fixed,
6. 80% of low and medium severity faults fixed,
7. Maximum of 50 known faults remain,
8. Maximum of 10 high severity faults predicted,
9. Time has run out,
10. Testing budget is used up.

Testing as a Service

noreply@blogger.com (Saurabh) — Tue, 19 Oct 2010 06:05:00 +0000

Testing as a Service (TaaS, typically pronounced 'tass') is a model of software testing whereby a provider undertakes the activity of software testing applications/solutions for customers as a service on demand. Testing as a Service involves the on-demand test execution of well-defined suites of test material, generally on an outsourced basis. The execution can be performed either on client site or remotely from the outsourced providers test lab/facilities.

To know more please visit TaaS

Cloud Testing Service Features

noreply@blogger.com (Saurabh) — Tue, 19 Oct 2010 05:37:00 +0000

To know about Cloud Testing Service Features please visit Cloud Testing Service Features

Skills Needed for Building Clouds

noreply@blogger.com (Saurabh) — Mon, 18 Oct 2010 04:32:00 +0000

By Mike DiPetrillo, Global Cloud Architect, VMware

1) Networking - Networking is about the most complex piece of VMware's cloud tools. Our product manager likes to call it "flexible" which it really is (and powerful) but it's also complex. Giving end users the ability to configure their own network segments on-the-fly complete with VLAN IDs is something that would scare most network admins and yet this is something that we need to tackle to get to "true cloud". I usually suggest to customers that they go and engage their network team early on in the cloud building process and then recruit the best of the networking engineers to be on the cloud team.

2) Storage - Storage is another area that can get complex. How do you make it so end users don't have to care about the underlying storage and yet land on the right volume from a performance perspective? And don't even get me started on movement of data from one place to another or backup. All of these things are going to require an ace storage engineer on the cloud team.

3) Programming Skills - You don't need some uber code monkey on the team but you do need someone that understands APIs, how to use them, and how you would go about plugging everything together. Automation is the name of the game in the guts of cloud and that's why tools like BMC Atrium Orchestrator, VMware vCenter Orchestrator, and HPOO have become centerpieces in the cloud. Most of these are based on Java or Javascript so find someone who can at least start there. And since nearly everything in cloud land seems to be going the path of REST it would be great to get someone that knows that and XML really well.

So those are my three core skill sets that I tell people to go out and find. There are more you could add to the list such as security or billing or portal design but those can be from people that augment the core team. If you find people in the above core skill sets then you'll be well on your way to architecting a successful cloud build out.

To know more plz visit vmware

Quality Assurance Activities

noreply@blogger.com (Saurabh) — Mon, 13 Sep 2010 07:28:00 +0000