410245(B): Software Testing and Quality Assurance (Elective-II)

1. Teaching Scheme: TH: 03 Hours/Week Examination Scheme: In-Sem (Paper): 30 Marks End-Sem (Paper): 70 Marks 410245(B):Software Testing and Quality Assurance(Elective-II) B.E. Computer Engineering Sem-I

2. Unit-IV: Selenium Tool • Introduction • Selenium Tools • Advantages of Selenium • Disadvantages of Selenium

3. Introduction • Selenium is an open-source and a portable automated software testing tool for testing web applications. It has capabilities to operate across different browsers and operating systems. It is a method by which management and employees can become involved in the continuous improvement of the production of goods and services. • Selenium is not just a single tool but a set of tools that helps testers to automate web-based applications more efficiently.

4. Selenium Tools.. • Selenium IDE • Selenium Integrated Development Environment (IDE) is a Firefox plugin that lets testers to record their actions as they follow the workflow that they need to test.

5. Selenium Tools.. • Selenium RC • Selenium Remote Control (RC) was the flagship testing framework that allowed more than simple browser actions and linear execution. It makes use of the full power of programming languages such as Java, C#, PHP, Python, Ruby and PERL to create more complex tests.

6. Selenium Tools.. • Selenium WebDriver • Selenium WebDriver is the successor to Selenium RC which sends commands directly to the browser and retrieves results.

7. Selenium Tools.. • Selenium Grid • Selenium Grid is a tool used to run parallel tests across different machines and different browsers simultaneously which results in minimized execution time.

8. Advantages of Selenium

9. Disadvantages of Selenium

10. Selenium Tool Suite

11. Selenium-IDE.. • The Selenium-IDE is an easy-to-use Firefox plug-in to develop Selenium test cases. It provides a Graphical User Interface for recording user actions using Firefox which is used to learn and use Selenium, but it can only be used with Firefox browser as other browsers are not supported. • However, the recorded scripts can be converted into various programming languages supported by Selenium and the scripts can be executed on other browsers as well.

12. Selenium-IDE Features

13. Product Quality Metrics.. • Software quality consists of two levels: • Intrinsic product quality • customer satisfaction • The metrics that covers both levels are: • Mean Time to Failure • Defect Density • Customer Problems • Customer Satisfaction

14. Product Quality Metrics.. • Mean Time to Failure: It is the time between failures. This metric is mostly used with safety critical systems such as the airline traffic control systems, and weapons. • Defect Density: It measures the defects relative to the software size expressed as lines of code or function point, etc. i.e., it measures code quality per unit. This metric is used in many commercial software systems.

15. Product Quality Metrics.. 3. Customer Problems: It measures the problems that customers encounter when using the product. It contains the customer’s perspective towards the problem space of the software, which includes the non-defect oriented problems together with the defect problems. The problems metric is usually expressed in terms of Problems per User-Month (PUM).

16. Product Quality Metrics.. PUM = Total Problems that customers reported (true defect and non-defect oriented problems) for a time period + Total number of license months of the software during the period Where, Number of license-month of the software = Number of install license of the software × Number of months in the calculation period • PUM is usually calculated for each month after the software is released to the market, and also for monthly averages by year.

17. Product Quality Metrics.. 4. Customer Satisfaction: • Customer satisfaction is often measured by customer survey data through the five-point scale, • Very satisfied • Satisfied • Neutral • Dissatisfied • Very dissatisfied • Satisfaction with the overall quality of the product and its specific dimensions is usually obtained through various methods of customer surveys.

18. Ishikawa’s 7 Basic Tools.. • Ishikawa's 7 Basic Tools of Quality is a designation given to a fixed set of graphical techniques identified as being most helpful troubleshooting issues related to quality. • They are called basic because they are used easily by people with little formal training in statistics.

19. Ishikawa’s 7 Basic Tools.. • The seven tools are: • Check sheet (Checklist) • Histogram • Pareto chart • Control chart • Scatter diagram • Stratification (alternately, flow chart or run chart) • Cause-and-effect diagram (also known as the "fishbone" or Ishikawa diagram) • This set of tools was first emphasized by Kaoru Ishikawa, a professor of engineering at Tokyo University and “father” of Quality Circles

20. 1. Check Sheet (Checklist).. • A check sheet can be introduced as the most basic tool for quality. • A check sheet is basically used for gathering and organizing data. • When this is done with the help of software packages such as Microsoft Excel, you can derive further analysis graphs and automate through macros available. • The check sheets are three major types, such as Defect-Location, Tally and Defect Cause check sheets. • One can always use a paper-based check sheet when the information gathered is only used for backup or storing purposes other than further processing.

22. 2. Histogram.. • Histogram is used for illustrating the frequency and the extent in the context of two variables. • Histogram is a chart with columns. This represents the distribution by mean. If the histogram is normal, the graph takes the shape of a bell curve. • If it is not normal, it may take different shapes based on the condition of the distribution. Histogram can be used to measure something against another thing. Always, it should be two variables. • Consider the example: The following histogram shows morning attendance of a class. The X-axis is the time of the day and the Y-axis the number of students.

24. 3. Pareto Charts.. • Definition: Pareto Diagram is a bar graph used to arrange information in such way that priorities for process improvement can be established. • The principal was developed by Vilfredo Pareto, an Italian economist and sociologist. • The fundamental idea behind the use of Pareto Diagram is Quality Improvement. • This helps you to work on the propriety issues in order to get the condition under control.

26. 4. Control Charts.. • Control chart is the best tool for monitoring the performance of a process. These types of charts can be used for monitoring any processes related to function of the organization. • These charts allow you to identify the following conditions related to the process that has been monitored. • Stability of the process • Predictability of the process • Identification of common cause of variation • Special conditions where the monitoring party needs to react

28. 5. Scatter Diagram.. • The scatter diagram helps to identify the existence of a measurable relationship between two items by measuring them in pairs and plotting them on a graph. • It visually shows the correlation between the two sets of measurement. • Two sets of data are plotted on a graph. With the Y-axis being used for the variable to be predicted (effect) and the X-axis being used for the variable to make the prediction (Cause).

31. 6. Flow Charts • This is one of the basic quality tool that can be used for analyzing a sequence of events. The tool maps out a sequence of events that take place sequentially or in parallel. The flow chart can be used to understand a complex process in order to find the relationships and dependencies between events. • You can also get a brief idea about the critical path of the process and the events involved in the critical path. • Flow charts can be used for any field to illustrate complex processes in a simple way. There are specific software tools developed for drawing flow charts, such as MS Visio.

33. 7. Cause and Effect Diagram.. • Cause and effect diagrams (Ishikawa Diagram) are used for understanding organizational or business problem causes. • Organizations face problems everyday and it is required to understand the causes of these problems in order to solve them effectively. Cause and effect diagrams exercise is usually a teamwork. • A brainstorming session is required in order to come up with an effective cause and effect diagram. • All the main components of a problem area are listed and possible causes from each area is listed.