PagKis - Software Testing & Quality
An execellent blog and online resource centre for Software Testing and quality assurance containing best of the best information for software testing and QA. See my daily posts on this blog and keep updated yourself with latest trends. Give your views also. Leave your comments... Happy Testing !! |
|
Statistics
Unique Visitors:
Total Unique Visitors:
Outgoing:
Total Outgoing: |
44
0
52
2617 |
|
|
Articles from PagKis - Software Testing & Quality |
Test Automation
2007-10-08 09:47:00
Often when a test automation tool is introduced to a project, the expectations for the return on investment are very high. Project members anticipate that the tool will immediately narrow down the scope for software testing effort, meaning reducing cost and schedule. However, I have seen several implementations of test automation are fail - miserably.The following very simple factors largely influence the effectiveness of automated testing, and if not taken into account, the results is usually a lot of lost effort, and very expensive shelfware.Scope - It is not practical to try to automate every test, nor is there the time available generally. Pick very carefully the functions/areas of the application that are to be automated. Preparation Timeframe - The preparation time for automated test scripts has to be taken into account. In general, the preparation time for automated test scripts can be up to 2/3 times longer than for manual testing. In reality, chances are that initially the too ...
|
Test Director
2007-10-07 13:31:00
It is a Global Test Management tool, the industry’s first global test management solution. It helps organizations deploy high-quality applications more quickly and effectively. It has four modules: RequirementsTest PlanTest LabDefectsThese modules are seamlessly integrated, allowing for a smooth information flow between various testing stages. The completely Web-enabled TestDirector supports high levels of communication and collaboration among distributed testing teams, driving a more effective, efficient global application-testing process. Web-based Site Administrator: The Site Administrator includes tabs for managing projects, adding users and defining user properties, monitoring connected users, monitoring licenses and monitoring TestDirector server information. Domain Management: TestDirector projects are now grouped by domain. A domain contains a group of related TestDirector projects, and assists you in organizing and managing a large number of projects. Enhanced Reports and Gr ...
|
Top down Testing vs Bottom up Testing
2007-10-06 03:52:00
Top down Testing: In this approach testing is conducted from main module to sub module. if the sub module is not developed a temporary program called STUB is used for simulate the submodule.Advantages:Advantageous if major flaws occur toward the top of the program. Once the I/O functions are added, representation of test cases is easier. Early skeletal Program allows demonstrations and boosts morale. Disadvantages:Stub modules must be produced Stub Modules are often more complicated than they first appear to be. Before the I/O functions are added, representation of test cases in stubs can be difficult. Test conditions ma be impossible, or very difficult, to create. Observation of test output is more difficult. Allows one to think that design and testing can be overlapped. Induces one to defer completion of the testing of certain modules. Bottom up testing: In this approach testing is conducted from sub module to main module, if the main module is not developed a temporary program calle ...
|
Usability Testing Lab
2007-10-05 13:55:00
In the usability lab, users are asked to perform a few tasks (functions) with the product being evaluated. There are the people who are actual users of the product. All their actions are directly observed and captured – video recorded for detailed analysis later. The lab is equipped to support the systematic observation and analysis of human-computer interaction. The lab has three sections: Test section Control section Observation section Test Section: Here, an actual or representative user interacts with the product. A camera records the user’s body language and hand movements on the keyboard, mouse and manuals. The screen interactions are captured live via a scan converter. Control Section: Here, a remote control unit is used to control the camera angle and zoom, ensuring that all data of interest is captured even if the user moves. Also, outputs from the camera and scan converter are monitored and mixed as required, using a video mixer. Observation section: Usability engineers w ...
|
Testing Principles
2007-10-05 13:51:00
- A necessary part of a test case is a definition of the expected output or result. - A programmer should avoid attempting to test his or her own program. - A programming organization should not test its own programs. - Thoroughly inspect the results of each test. - Test cases must be written for input conditions that are invalid and unexpected, as well as for those that are valid and expected.- Examining a program to see if it does not do what it is supposed to do is only half the battle; the other half is seeing whether the program does what it is not supposed to do.- Avoid throwaway test cases unless the program is truly a throwaway program.- Do not plan a testing effort under the tacit assumption that no errors will be found.- The probability of the existence of more errors in a section of a program is proportional to the number of errors already found in that section.- Testing is an extremely creative and intellectually challenging task. ...
|
Testing - NAS (Network Attached Storage)
2007-10-04 09:51:00
All media appear to be going digital these days, including your photos, music, home movies, and even television. But where do you store your ever expanding media collection so that the rest of your family can access it seamlessly across your home network? Or how do you make files accessible to your networked coworkers in a small office without investing in an expensive file server? Enter the relatively new product category of network-attached storage (NAS). While storage capacity, functionality, and ease of use are all important variables to consider, performance should not be overlooked. Not all NAS devices are created equal, and you'll really feel the difference when you're waiting for those huge files to open. In order to deliver relevant performance evaluations of NAS devices, companies Labs puts them through their paces with the real-world tasks of reading and writing files.Test environment: Network-attached storage devices are tested using a Netgear GS605 five-port Gigabit Ethe ...
|
QTP Interview Questions
2007-10-03 03:23:00
1. How Does Run time data (Parameterization) is handled in QTP?A). You can then enter test data into the Data Table, an integrated Spreadsheet with the full functionality of Excel, to manipulate data Sets and create multiple test iterations, without programming, to Expand test case coverage. Data can be typed in or imported from Databases, spreadsheets, or text files. 2) What is keyword view and Expert view in QTP?A) Quick Test’s Keyword Driven approach, test automation experts Have full access to the underlying test and object properties, via an integrated scripting and debugging environment that is round-trip synchronized with the Keyword View.Advanced testers can view and edit their tests in the Expert View, which reveals the underlying industry-standard VBScript that Quick Test Professional automatically generates. Any changes made in the Expert View are automatically synchronized with the Keyword View. 3) Explain about the Test Fusion Report of QTP?A) Once a tester has run a tes ...
|
Validation vs Verification
2007-10-02 05:03:00
Validation: The process of evaluating software at the end of the software development process to ensure compliance with software requirements. It is actual testing of the application.1. Am I building the right product.2. Determining if the system complies with the requirements and performs functions for which it is intended and meets the organization’s goals and user needs. It is traditional and is performed at the end of the project.3. Am I accessing the right data (in terms of the data required to satisfy the requirement).4. High level activity.5. Performed after a work product is produced against established criteria ensuring that the product integrates correctly into the environment.6. Determination of correctness of the final software product by a development project with respect to the user needs and requirements. Verification: The process of determining whether of not the products of a given phase of the software development cycle meet the implementation steps and can be trace ...
|
Pairwise Testing
2007-10-02 00:52:00
Pairwise testing is an effective test case generation technique that is based on the observation that most faults are caused by interactions of at most two factors. Pairwise-generated test suites cover all combinations of two therefore are much smaller than exhaustive ones yet still very effective in finding defects.All-pairs testing or pairwise testing is a combinatorial software testing method that, for each pair of input parameters to a system (typically, a software algorithm) tests all possible discrete combinations of those parameters. Using carefully chosen test vectors, this can be done much faster than an exhaustive search of all combinations of all parameters, by "parallelizing" the tests of parameter pairs. The number of tests is typically O(nm), where n and m are the number of possibilities for each of the two parameters with the most choices.The reasoning behind all-pairs testing is this: the simplest bugs in a program are generally triggered by a single input parameter. Th ...
|
Black Box Testing
2007-10-01 04:06:00
Black box is a test design method. Black box testing treats the system as a "black-box", so it doesn't explicitly use Knowledge of the internal structure. Or in other words the Test engineer need not know the internal working of the “Black box”. It focuses on the functionality part of the module.Some people like to call black box testing as behavioral, functional, opaque-box, and closed-box. While the term black box is most popularly use, many people prefer the terms "behavioral" and "structural" for black box and white box respectively. Behavioral test design is slightly different from black-box test design because the use of internal knowledge isn't strictly forbidden, but it's still discouraged. Personally we feel that there is a trade off between the approaches used to test a product using white box and black box types.There are some bugs that cannot be found using only black box or only white box. If the test cases are extensive and the test inputs are also from a large ...
|
White Box Testing
2007-09-30 00:28:00
What is WBT?White box testing involves looking at the structure of the code. When you know the internal structure of a product, tests can be conducted to ensure that the internal operations performed according to the specification. And all internal components have been adequately exercised. In other word WBT tends to involve the coverage of the specification in the code.Code coverage is defined in six types as listed below:Segment coverage – Each segment of code b/w control structure is executed at least once.Branch Coverage or Node Testing – Each branch in the code is taken in each possible direction at least once.Compound Condition Coverage – When there are multiple conditions, you must test not only each direction but also each possible combinations of conditions, which is usually done by using a ‘Truth Table’Basis Path Testing – Each independent path through the code is taken in a pre-determined order.Data Flow Testing (DFT) – In this approach you track the specific v ...
|
[First] « Prev 1 2 3 Next » [Last]
4248 blogs in our database.
Statistics resets every week.
|
|