Automating Software Tests Using Selenium

Hugo Peres

• Publisher: Hugo Peres
• eBook ISBN: 9788595131385
• Topic: Computer Science
• Subtopic: Quality Assurance & Testing
• Index: Computer Science

Automating Software Tests Using Selenium is a practical manual aimed at all professionals and companies in the systems area and who aim to improve the quality of their services and / or products in a simple, efficient and low cost.In this book you will find the features that the Selenium tool provides to implement a robust automated testing environment, such as: writing / executing test scripts, exporting / importing test scripts into a test project, running tests simultaneously on different platforms and browsers.Innovate your way to test software, embarking on this incredible world of automation and see through the results how machines can facilitate your day-to-day tasks

1. CONCEPT FOUNDATIONS AND SOFTWARE TESTING

“There is never time to do the right thing, but there is always time to do it again.”

1.1 SOFTWARE QUALITY

Defining quality is not trivial as it seems. To Pressman (2011), software quality
and something that needs to be defined at a more pragmatic level. For this, it is based on the concept of David Gravai (Gar84), which defines the theme in five different points of view:

Transcendental Vision: It maintains that quality is something that is recognized immediately, but cannot be defined explicitly.

User Vision: See quality in terms of the specific goals of an end user. If a product meets targets, features quality.

Manufacturer Vision: Sets quality in terms of original product specification. If the product fulfill the expectations, it features quality.

Product Overview: It suggests that quality can be linked to inherent characteristics of a product, for example, functions and resources.

Value Vision: Measures quality based on how much a customer would be willing to pay for the product.

1.1.1 SOFTWARE QUALITY

The ISO/IEC 25000¹, known as SQuaRE (System and Software Quality Requirements and Evaluation), joined the rules ISO/IEC 9126 (model) and ISO/IEC 14598 (process) with the objective of improving the quality evaluation of the software.

In the ISO/IEC 2501n division, we found the model ISO/IEC 25010, which defines the characteristics and subcharacteristics that a software needs to have to be considered a “quality software”.

• Functional Suitability

• Completeness: Capacity which features cover all user requirements.
• Accuracy: Capacity which the system presents correct results.
• Suitability: Capacity which the functionalities have in adapting to the requirements of the user.

• Performance Efficiency

• Behavior Time: Time response capacity, processing or transfer of requests made by the system.
• Use of Resources: Capacity which resources (processor, memory, etc.) are used by the system.
• Capacity: Capacity in which the system supports transactions.

• Compatibility

• Coexistence: Capacity which the software performs when sharing the same environment with other softwares.
• Interoperability: Capacity which the software communicates (exchange of information) with each other.

.

• Usability

• Recogntability: Capacity which the user recognizes if the software meets their needs well.
• Apprehensibility: Ability which software can be used by specific users to meet specific learning-level goals.
• Operationality: The user's ability to operate the software.
• Protection against errors: Capacity which the system has and avoid errors of handling by the user.
• Aesthetics of the interface: Capacity which the interface of the system has in interacting in a satisfactory and pleasant way with the user.
• Accessibility: Capacity which the software has to be operated by different types of users, different needs.

• Reliability

• Maturity: The ability of the software to meet Reliability needs in normal operations.
• Fault Tolerance: Ability of the software to work well, even with hardware failure or other software.
• Recoverability: Ability of the software to return to its normal state after interruptions.

• Security

• Confidentiality: The ability of the software to provide information only to authorized users.
• Integrity: The ability of the software to prevent unauthorized access or alterations.
• Non-repudiation: Software's ability to recognize the veracity of certain actions and events so as not to repudiate them at another time.
• Accountability: Software's ability to assign an action to an entity.
• Authenticity: Ability of the software to recognize the true identity of a resource.

• Maintainability

• Modularity: The ability of the software to have its components changed without any impact between them.
• Reuse: Capacity that the asset has in being reused in more than one system.
• Analysability: Ability of the software to measure the impacts of component exchanges as well as to identify the correct corrections.
• Modifiability: Software capability to not present failures after modifications, either by improvement or correction of errors.
• Testability: Software's ability to meet test criteria.

• Portability

• Adaptability: Software's ability to adapt to a wide range of environments.
• Instability: Ability of the software to be installed and uninstalled from an environment.
• Substitutability: Ability of the software has to be replaced by another in lesser possible impact.

1.1.2 THE SOFTWARE QUALITY DILEMMA

About Quality in Organizations, Pressman (2011) quote an interview (Ven03)
posted on the internet, where Bertrand Meyer
discusses what we call a quality dilemma:

If we produce a poor quality software system, we lose because nobody will want to buy them. If, on the other hand, we spend infinite time, an overwhelming effort and large sums of money to build absolutely perfect software, then it will take a long time to complete, and the cost of production will be so high that we will go bankrupt. Either we miss the market opportunity or we simply exhaust all our resources. In this way, professionals in ...

Table of contents

• 1. CONCEPT FOUNDATIONS AND SOFTWARE TESTING
• 2. WELCOME TO THE AUTOMATION ERA
• 3. EXPLORING SELENIUM RESOURCES
• 4. AGAINST BUGS THERE ARE NO ARGUMENTS
• 5. FINAL CONSIDERATIONS
• REFERENCES
• GLOSSARY
• ANNEXES
• APPENDICES