Software testing lab file

User can pay using netbanking or card. How do I purchase video? Email us on info softwaretestinglab. Our executive will call you. How do I get invoice? Once your payment is done, receipt will be sent in 4 to 5 business hours. Videos Manual Testing. Software Testing lab one of the Best Training Website. I am very happy to say thankful to Software Testing Lab..

Nikul Patel. Great Experience :. Assume that the upper limit for the size of any side is Derive test cases for your program based on boundary-value analysis, execute the test cases and discuss the results.

For any queries Contact: The basic idea is to use input variables at their minimum, just above minimum, nominal, just below their maximum and maximum. Considering Triangle program, we have three variables a, b and c.

Each variables value ranges from 1 to Again keeping variable b and c as nominal combine with 5 values of a. Analyse it from the perspective of boundary value testing, derive different test cases, execute these test cases and discuss the test results.

Analyze it from the perspective of boundary value testing, derive different test cases, execute these test cases and discuss the test results. Assume the upper limit for the size of any side is Derive test cases for your program based on equivalence class partitioning, execute the test cases and discuss the results.

Analyse it from the perspective of equivalence class testing, derive different test cases, execute these test cases and discuss the test results. Analyze it from the perspective of equivalence class value testing, derive different test cases, execute these test cases and discuss the test results. Enter valid values for day and year from equivalence WR5 classes and invalid value for month. Enter valid values for day and year from equivalence SR2 classes and invalid value for month.

SR10 Enter valid value for year from equivalence classes and Day, Month out of invalid values for day and month. SR12 Enter valid value for day from equivalence classes and Month, Year out of 15 13 Valid invalid values for month and year. Derive test cases for your program based on decision table approach, execute the test cases and discuss the results. Enter the values of a, b and c such that value of b is greater Case 2 2 8 3 Not a triangle Valid than sum of a and c.

Enter the values of a, b and c such that value of c is greater Case 3 2 4 7 Not a triangle Valid than sum of a and b. Enter the values of a, b and c such that values of a,b and c Case 4 5 5 5 Equilateral Valid are equal. The GUI map consists of files maintained separately from your test scripts. If the user interface of your application changes, you have to update only the GUI map, instead of hundreds of tests.

This allows you to easily reuse your Context Sensitive test scripts on future versions of your application. To run a test, you simply play back the test script. WinRunner emulates a user by moving the mouse pointer over your application, selecting objects, and entering keyboard input.

WinRunner reads the object descriptions in the GUI map and then searches in the application being tested for objects matching these descriptions. It can locate objects in a window even if their placement has changed. Analog Analog mode records mouse clicks, keyboard input, and the exact x- and y-coordinates traveled by the mouse.

When the test is run, WinRunner retraces the mouse tracks. Use Analog mode when exact mouse coordinates are important to your test, such as when testing a drawing application. Alternatively, you can add descriptions of individual objects to the GUI map by clicking objects while recording a test. Create Tests Next is creation of test scripts by recording, programming, or a combination of both.

While recording tests, insert checkpoints where we want to check the response of the application being tested. We can insert checkpoints that check GUI objects, bitmaps, and databases. During this process, WinRunner captures data and saves it as expected results—the expected response of the application being tested. Debug Tests One can set breakpoints, monitor variables, and control how tests are run to identify and isolate defects. Test results are saved in the debug folder, which can be discarded once debugging is finished.

When WinRunner runs a test, it checks each script line for basic syntax errors, like incorrect syntax or missing elements in If, While, Switch, and For statements. Run Tests Tests can be run in Verify mode to test the application. Each time WinRunner encounters a checkpoint in the test script, it compares the current data of the application being tested to the expected data captured earlier.

If any mismatches are found, WinRunner captures them as actual results. View Results Following each test run, WinRunner displays the results in a report. The report details all the major events that occurred during the run, such as checkpoints, error messages, system messages, or user messages. If mismatches are detected at checkpoints during the test run, we can view the expected results nd the actual results from the Test Results window.

In cases of bitmap mismatches, one can also view a bitmap that displays only the difference between the expected and actual results. We can view results in the standard WinRunner report view or in the Unified report view.

The WinRunner report view displays the test results in a Windows-style viewer. Report Defects If a test run fails due to a defect in the application being tested, one can report information about the defect directly from the Test Results window.

This information is sent via e-mail to the quality assurance manager, who tracks the defect until it is fixed. Using Winrunner Window Before you begin creating tests, you should familiarize yourself with the WinRunner main window. From the Welcome window you can create a new test, open an existing test, or view an overview of WinRunner in your default browser. The Main WinRunner Window The main WinRunner window contains the following key elements: WinRunner title bar Menu bar, with drop-down menus of WinRunner commands Standard toolbar, with buttons of commands commonly used when running a test User toolbar, with commands commonly used while creating a test Status bar, with information on the current command, the line number of the insertion point and the name of the current results folder The Standard toolbar provides easy access to frequently performed tasks, such as opening, executing, and saving tests, and viewing test results.

Standard Toolbar The User toolbar displays the tools you frequently use to create test scripts. By default, the User toolbar is hidden. When you create tests, you can minimize the WinRunner window and work exclusively from the toolbar.

The User toolbar is customizable. When you re-open WinRunner, the User toolbar appears as it was when you last closed it. The commands on the Standard toolbar and the User toolbar are described in detail in subsequent lessons. Note that you can also execute many commands using softkeys. Softkeys are keyboard shortcuts for carrying out menu commands. You can configure the softkey combinations for your keyboard using the Softkey Configuration utility in your WinRunner program group.

Now that you are familiar with the main WinRunner window, take a few minutes to explore these window components before proceeding to the next lesson. Selenium Selenium provides a rich set of testing functions specifically geared to the needs of testing of a web application.

These operations are highly flexible, allowing many options for locating UI elements and comparing expected test results against actual application behavior. Selenium Components Selenium is composed of three major tools. Each one has a specific role in aiding the development of web application test automation.

Selenium-Grid Selenium-Grid allows the Selenium-RC solution to scale for large test suites or test suites that must be run in multiple environments. With Selenium-Grid, multiple instances of Selenium-RC are running on various operating system and browser configurations; Each of these when launching register with a hub. When tests are sent to the hub they are then redirected to an available Selenium-RC, which will launch the browser and run the test.

This allows for running tests in parallel, with the entire test suite theoretically taking only as long to run as the longest individual test. Flexibility and Extensibility Selenium is highly flexible.

This allows users to customize the generated code to fit in with their own test frameworks. Finally, Selenium is an Open Source project where code can be modified and enhancements can be submitted for contribution. Test Suites A test suite is a collection of tests. Often one will run all the tests in a test suite as one continuous batch-job.

The syntax again is simple. An HTML table defines a list of tests where each row defines the filesystem path to each test.

An example tells it all. Test suites can also be maintained when using Selenium-RC. This is done via programming and can be done a number of ways. Additionally, if C is the chosen language, Nunit could be employed. If using an interpreted language like Python with Selenium-RC than some simple programming would be involved in setting up a test suite.

Few typical Selenium commands. Called automatically when clickAndWait is used. Multiple users can access this database and query, add and manage these bugs. Bugzilla essentially comes to the rescue of a group of people working together on a product as it enables them to view current bugs and make contributions to resolve issues.

Its basic repository nature works out better than the mailing list concept and an organized database is always easier to work with. Bugzilla is very adaptable to various situations. Known uses currently include IT support queues, Systems Administration deployment management, chip design and development problem tracking both pre-and-post fabrication , and software and hardware bug tracking for luminaries such as Redhat, NASA, Linux-Mandrake, and VA Systems.

Combined with systems such as CVS, Bugzilla provides a powerful, easy-to-use solution to configuration management and replication problems. Bugzilla can dramatically increase the productivity and accountability of individual employees by providing a documented workflow and positive feedback for good performance.

The bugzilla utility basically allows to do the following: Add a bug into the database Review existing bug reports Manage the content Bugzilla is organised in the form of bug reports that give all the information needed about a particular bug. A bug report would consist of the following fields. At a minimum, we should change the following items, to suit our particular need: Click Parameters at the bottom of the page.

Under Required Settings, add an email address in the maintainer field. Click Save Changes. In the left side Index list, click Email.

If evaluating a click2try application, select Test. In the left side Index list, click Bug Change Policies. Select On for commentoncreate, which will force anyone who enters a new bug to enter a comment, to describe the bug.

Click Default Preferences at the bottom of the page. Select the display order from the drop-down list next to the When viewing a bug, show comments in this order field. Click Submit Changes. Creating a New User Before entering bugs, make sure we add some new users. We can enter users very easily, with a minimum of information. To create a new user: 1. Click Users. Click add a new user. Enter the Login name, in the form of an email address. Enter the Real name, a password, and then click Add.

Select the Group access options. Click Update when done with setting options. Impersonating a User Perhaps the user is on vacation, or is temporarily assigned to another project. We can impersonate the user to create or manage bugs that belong to that user.

We should delete this and create a new product. To add a product: 1. At the bottom of the page, click Products. In the TestProduct listing, click Delete. Click Yes, Delete. Now click Add a product. Enter a description. Click Add. Adding Product Components Products are comprised of components. Software products, in particular, are typically made up of many functional components, which in turn are made up of program elements, like classes and functions. Often, they will review the bugs as they are reported, in order to redirect them to the appropriate developer or even another team, to review the priority and severity supplied by the reporter, and sometimes to reject bugs as duplicates or enhancement requests, for example.

To add a component: 1. Click the link add at least one component in the message that appears after creating a new product. Enter the Component name. Enter a Description. Enter a default assignee. Remember to enter the assignee in the form of an email address. Modifying Default Field Values Some of these may work just fine for our product. Others may not. We can modify the values of these fields, adding new values and deleting old ones.

To modify default field values: 1. At the bottom of the page, in the Edit section, click Field Values. Click the link, in this case OS, for the field we want to edit.

The OS field contains a list of operating system names. We are going to add browsers to this list. In reality, we might create a custom field instead, but for the sake of this example, just add them to the OS list.