Accessibility testing is the technique of making sure that your product is accessibility compliant. There could be many reasons why your product needs to be accessibility compliant as stated above. Typical accessibility problems can be classified into following four groups, each of them with different access difficulties and issues: Visual impairments 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. Motor skills Such as the inability to use a keyboard or mouse, or to make fine movements. Hearing impairments Such as reduced or total loss of hearing Cognitive abilities Such as reading difficulties, dyslexia or memory loss. Development...

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

0 Comments

Tags: accessibility testing, Manual testing

Usability testing is a technique used to evaluate a product by testing it on users. This can be seen as an irreplaceable usability practice, since it gives direct input on how real users use the system. This is in contrast with usability inspection methods where experts use different methods to evaluate a user interface without involving users.Usability testing focuses on measuring a human-made product's capacity to meet its intended purpose. Examples of products that commonly benefit from usability testing are foods, consumer products, web sites or web applications, computer interfaces, documents, and devices. Usability testing measures the usability, or ease of use, of a specific object or set of objects, whereas general human-computer interaction studies attempt to formulate universal principl...

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

0 Comments

Tags: Manual testing, usability testing

Localization (L10N) is the process of customizing a software application that was originally designed for a domestic market so that it can be released in foreign markets. This process involves translating all native language strings to the target language and customizing the GUI so that it is appropriate for the target market. Depending on the size and complexity of the software, localization can range from a simple process involving a small team of translators, linguists, desktop publishers and engineers to a complex process requiring a Localization Project Manager directing a team of a hundred specialists. Localization is usually done using some combination of in-house resources, independent contractors and full-scope services of a localization company. ______________________________________________________________________________ Localization...

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

0 Comments

Tags: localization, Manual testing

Manual testing is the oldest and most rigorous type of software testing. Manual testing requires a tester to perform manual test operations on the test software without the help of Test automation. Manual testing is a laborious activity that requires the tester to possess a certain set of qualities; to be patient, observant, speculative, creative, innovative, open-minded, resourceful, unopinionated, and skillful. Manual testing is the process of manually testing software for defects. It requires a tester to play the role of an end user, and use most of all features of the application to ensure correct behavior. To ensure completeness of testing, the tester often follows a written test plan that leads them through a set of important test cas...

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

0 Comments

Tags: Manual testing

"V" Model is one of the SDLC Methodologies.In this methodology Development and Testing takes place at the same time with the same kind of information in their hands.Typical "V" shows Development Phases on the Left hand side and Testing Phases on the Right hand side.Development Team follow "Do-Procedure" to achive the goals of the company and Testing Team follow "check-Procedure" to verify them. Differences In V-Model and Waterfall Model In Waterfall Model the tester role will take place only in the test phase but in V-Model role will take place in the requirement phase itself Waterfall madel is a fixed process u can't make any changes in the requirement or in any phase.but in V-Model u can make any changes in the requirements V-model...

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

12 Comments

Tags: Manual testing, v model, waterfall model

Test execution/efficiency metrics gives the detailed information of test cases executions. Total number of test cases Total number of test cases execution Total number of test cases passed Total number of test cases failed Total number of test cases not tested Total number of test cases not applicable as these are depended on the test cases those are either not tested or failed test execution.blocked test cases...

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

0 Comments

Tags: Manual testing, Test execution

Defect reports are among the most important deliverables to come out of test. They are as important as the test plan and will have more impact on the quality of the product than most other deliverables from test. It is worth the effort to learn how to write effective defect reports. Effective defect reports will: . Reduce the number of defects returned from development . Improve the speed of getting defect fixes . Improve the credibility of test . Enhance teamwork between test and development Why do some testers get a much better response from development than others? Part of the answer lies in the defect report. Following a few simple rules can smooth the way for a much more productive environment. The objective is not to write the perfect defect report, but to write an effective defect report that conveys the proper message,...

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

0 Comments

Tags: defect report, Manual testing

“Priority” is associated with scheduling, and “severity” is associated with standards. “Priority” means something is afforded or deserves prior attention; a precedence established by order of importance (or urgency). “Severity” is the state or quality of being severe; severe implies adherence to rigorous standards or high principles and often suggests harshness; severe is marked by or requires strict adherence to rigorous standards or high principles, e.g. a severe code of behavior. The words priority and severity do come up in bug tracking. A variety of commercial, problemtracking/ management software tools are available. These tools, with the detailed input of software test engineers, give the team complete information so developers can understand the bug, get an idea of its ‘severity’, reproduce it and fix it. The fixes are based on project...

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

0 Comments

Tags: Manual testing, priority, severity

Defect Report Template A good defect report might have following sections. Headline One line description of the defect. Remember, A good headline will always be clear, related to the defect and give some hints on how critical defect could be. Product In most cases defect tracking system is used for more than one product. So specifying appropriate product and version is very important. Component Products are normally very complex, and can be divided into components. A defect report containing proper information about component can help managers in assigning it to appropriate person. Defect Type Defect type could be, functionality, specification, regression, UI etc. This classification can be used to analyze how defects are distributed in the system. Priority Priority is the impact of defect on business. This field gives an indication...

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

0 Comments

Tags: defect report, Manual testing

Let’s have first web testing checklist. 1) Functionality Testing 2) Usability testing 3) Interface testing 4) Compatibility testing 5) Performance testing 6) Security test...

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

0 Comments

Tags: Manual testing, web testing

What is Bug/Defect? Simple Wikipedia definition of Bug is: “A computer bug is an error, flaw, mistake, failure, or fault in a computer program that prevents it from working correctly or produces an incorrect result. Bugs arise from mistakes and errors, made by people, in either a program’s source code or its design.” Other definitions can be: An unwanted and unintended property of a program or piece of hardware, especially one that causes it to malfunction. or A fault in a program, which causes the program to perform in an unintended or unanticipated manner. Lastly the general definition of bug is: “failure to conform to specifications”. If you want to detect and resolve the defect in early development stage, defect tracking and software...

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

0 Comments

Tags: defect life cycle, Manual testing

Load testing -Load testing is a test whose objective is to determine the maximum sustainable load the system can handle. Load is varied from a minimum (zero) to the maximum level the system can sustain without running out of resources or having, transactions suffer (application- specific) excessive delay.   Stress testing - Stress testing is subjecting a system to an unreasonable load while denying it the resources (e.g., RAM, disc, mips, interrupts) needed to process that load. The idea is to stress a system to the breaking point in order to find bugs that will make that break potentially harmful. The system is not expected to process the overload without adequate resources, but to behave (e.g., fail) in a decent manner...

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

0 Comments

Tags: load, Manual testing, performance, stress

Smoke Testing: Software Testing done to ensure that whether the build can be accepted for through software testing or not. Basically, it is done to check the stability of the build received for software testing. Sanity testing: After receiving a build with minor changes in the code or functionality, a subset of regression test cases are executed that to check whether it rectified the software bugs or issues and no other software bug is introduced by the changes. Sometimes, when multiple cycles of regression testing are executed, sanity testing of the software can be done at later cycles after through regression test cycles. If we are moving a build from staging / testing server to production server, sanity testing of the software application can be done to check that whether the build is sane enough to move to further at production...

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

0 Comments

Tags: Manual testing, sanity, smoke

Re- test - Retesting means we testing only the certain part of an application again and not considering how it will effect in the other part or in the whole application. Regression Testing - Testing the application after a change in a module or part of the application for testing that is the code change will affect rest of the application. Re-Test You have tested an application or a product by executing a test case. The end result deviates from the expected result and is notified as a defect. Developer fixes the defect. The tester executes the same test case that had originally identified the defect to ensure that the defect is rectified. Regression TestDeveloper fixes the defect. Tester re-test the application to ensure that the defect is rectified. He also identifies a set of test cases whose test scenario sorrounds the defect to ensure...

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

0 Comments

Tags: Manual testing, Re-testing, Regression testing

Retesting Testing : re-execution of testcases on same application build with different inputs or test data. Retesting - Testing functionality after the bug is fixed with different set of inputs another definition Retesting:testing the same application to make sure that it does not create any defects and if it does creat defects we r going to fix the bugs and then comes regression testing.in other words retesting is performed to ensure that if at all the bugs were found we r going to perform regression testing.this means that retesting and regression testing are performed in a cyclic process or chain process. another definition Re-Testing-- New version of the application under test. Once the new version is ready for release, tests are rerun to ensure the previously found faults are actually been fixed. This is re-testing. It...

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

0 Comments

Tags: Manual testing, Retesting

Verification ensures the product is designed to deliver all functionality to the customer; it typically involves reviews and meetings to evaluate documents, plans, code, requirements and specifications; this can be done with checklists, issues lists, walkthroughs and inspection meetings. You CAN learn to do verification, with little or no outside help. Validation ensures that functionality, as defined in requirements, is the intended behavior of the product; validation typically involves actual testing and takes place after verifications are completed. Difference between Verification and Validation: Verification takes place before validation, and not vice versa. Verification evaluates documents, plans, code, requirements, and specifications. Validation, on the other hand, evaluates the product itself. The inputs of verification are checklists,...

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

0 Comments

Tags: Manual testing, Verification and Validation

Verification is preventing mechanism to detect possible failures before the testing begin. It involves reviews, meetings, evaluating documents, plans, code, inspections, specifications ...

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

0 Comments

Tags: Manual testing, verification

Quality Assurance: A set of activities designed to ensure that the development and/or maintenance process is adequate to ensure a system will meet its objectives. Quality Control: A set of activities designed to evaluate a developed work product. Testing: The process of executing a system with the intent of finding defects. (Note that the "process of executing a system" includes test planning prior to the execution of the test cases.) QA activities ensure that the process is defined and appropriate. Methodology and standards development are examples of QA activities. A QA review would focus on the process elements of a project - e.g., are requirements being defined at the proper level of detail. QC activities focus on finding defects in specific deliverables - e.g., are the defined requirements the right requirements Testing...

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

0 Comments

Tags: difference between Quality Assurance and Quality Control, Manual testing

Quality assurance is the process of verifying or determining whether products or services meet or exceed customer expectations. Quality assurance is a process-driven approach with specific steps to help define and attain goals. This process considers design, development, production, and service.The most popular tool used to determine quality assurance is the Shewhart Cycle, developed by Dr. W. Edwards Deming. This cycle for quality assurance consists of four steps: Plan, Do, Check, and Act. These steps are commonly abbreviated as PDCA.The four quality assurance steps within the PDCA model stand for: Plan: Establish objectives and processes required to deliver the desired results. Do: Implement the process developed. Check: Monitor and evaluate the implemented process by testing the results against the predetermined objectives...

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

0 Comments

Tags: Manual testing, Quality Assurance

Simple Wikipedia definition of Bug is: “A computer bug is an error, flaw, mistake, failure, or fault in a computer program that prevents it from working correctly or produces an incorrect result. Bugs arise from mistakes and errors, made by people, in either a program’s source code or its design.” Other definitions can be: An unwanted and unintended property of a program or piece of hardware, especially one that causes it to malfunction. or A fault in a program, which causes the program to perform in an unintended or unanticipated manner. Lastly the general definition of bug is: “failure to conform to specifications”. If you want to detect and resolve the defect in early development stage, defect tracking and software development phases should start simultaneously. We will discuss more on Writing effective bug report in another article....

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

0 Comments

Tags: defect and its reasons, Manual testing

Identify the different end users of the system and their interaction with the same. Capture the important scenarios for each end user. It’s good to note that we need to capture the story around the scenario and not just steps. Talk to different stake holders including the customers (incase if you have access) on how the feature might be used & capture the scenarios. Plan towards uncovering the critical issues of the system as early as possib...

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

0 Comments

Tags: Manual testing, role of tester

According to the British norm BS 7925-1: bug--generic term for fault, failure, error, human action that produces an incorrect result. Robert Vanderwall offers these formal definitions from IEEE 610.1. The sub-points are his own. mistake (an error): A human action that produces an incorrect result. - mistake made in translation or interpretation. - lots of taxonomies exist to describe errors. fault: An incorrect step, process or data definition. - manifestation of the error in implementation - this is really nebulous, hard to pin down the 'location' failure: An incorrect result. bug: An informal word describing any of the above. (Not IEEE) If you want the above in simple text:-A defect is for something that normally works, but it has something out-of-spec. On the other hand a Bug is something that was considered but...

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

0 Comments

Tags: Error- Defect and Failure, Manual testing

Software testing is a job for skilled persons and to test the software the person must at least have the knowledge of testing tools, logical and analytical ability and  quality approach towards the testing process.  along with Curiosity Detail oriented and thorough   Trouble-shooter Perseverance Creativity "Flexible" Perfectionists Good judgement (judgment) Persuasive Tact and Diplomacy source:-  techmanageronli...

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

0 Comments

Tags: Manual testing, Skills of testers

Debugging is the consequence of successful testing.     Debugging is finding the error and report it with the intention of fixing it via developer,known as Debugging.        Testing is the broader term which includes Static and Dynamic Testing. also Testing is nothing but finding an error/problem and its done by testers where as debugging is nothing but finding the root cause for the error/problem and that is taken care by developers. also take into consideration An Error is found by the developer. A defect is found by the tester. A bug is _ defect found by tester and accepted by the developer....

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

0 Comments

Tags: diff between Debugging and Testing, Manual testing

This can be a big debate. Developers testing their own code – what will be the testing output? All happy endings! Yes, the person who develops the code generally sees only happy paths of the product and don’t want to go in much details. The main concern of developer testing is – misunderstanding of requirements. If requirements are misunderstood by developer then no matter at what depth developer test the application, he will never find the error. The first place where the bug gets introduced will remain till end, as developer will see it as functionality. Optimistic developers – Yes, I wrote the code and I am confident it’s working properly. No need to test this path, no need to test that path, as I know it’s working properly. And right here developers skip the bugs. Developer vs Tester: Developer always wants to see his code working...

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

0 Comments

Tags: Developer vs Tester

Testing is required to check that the application satisfies the requirements. OR Testing is required to Build a Quality Product. OR Testing is required to Deliver a quality product. ORTesting will give confidence for the software development company that the software will work satisfactorily in client environmant. Testing will improve the software quality. Testing will also reduces the maintanance cost also. Even the client of the software will get confidence on the software.  OR  without having to spend more time and cost we produce quality product  Due to psychological behaviour of a man is "a man can recognizing other faults easily" OR TESTING is VERY IMPORTANT BECAUSE 1. TO AVOID USER TO FIND BUGS 2. TO KEEP REALIABILITY IN UR PRODUCT 3. TO KEEP QUALITY...

Read more »

These icons link to social bookmarking sites where readers can share and discover new web pages.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

0 Comments

Tags: WHY TESTING IS NEEDED