Abstracta On Testing: Sesiones Exploratorias

Exploratory Testing Sessions Overview

In this section, the speaker introduces the concept of exploratory testing sessions and their significance in software testing.

Exploring Exploratory Testing

• Explains exploratory testing as a technique involving documenting and testing simultaneously.

• Discusses different styles of exploratory testing, such as ad hoc and strategy-based.

• Focuses on session-based exploratory testing as a comprehensive technique used at Abstracta.

• Defines sessions as the basic unit of work in testing with defined timeframes and clear objectives.

• Highlights the importance of short session durations for sustained focus and comprehensive testing coverage.

Example Session Structure

This part delves into an example of structuring a session for exploratory testing, outlining key components and considerations.

Structuring a Testing Session

• Defining a clear objective for the mission to be tested during the session.

• Detailing the devices, operating systems, and functionalities to be included in the session area.

• Noting the date, start/end times, duration breakdown, and task division within the session.

• Recording time spent on actual testing versus setup/configuration activities during the session.

• Documenting test data used, test notes summarizing functionality tested, risks identified, incidents reported, and any issues encountered.

Practical Application with Open Card

Demonstrating how to apply the structured approach to exploratory testing using Open Card as an example scenario.

Applying Testing Principles

• Defining a specific mission: verifying interaction with product options without logging into Open Card site.

Objective and Test Planning

In this section, the speaker discusses the objectives of testing and the importance of detailed test planning before execution.

Objectives and Test Information

• When preparing for testing, it is essential to fill in information such as the operating system to be used during testing, functionalities to be tested, start date, and tester responsible.

• Recommendations are provided on how to efficiently document test details without interrupting the testing process. Suggestions include taking notes on a draft document during testing and later transferring them accurately into the test session log.

Testing Execution

• It is advised to note down any bugs or improvements identified during testing. If a project uses incident reporting tools, incidents can be reported there with a link included in the test session log.

• The speaker introduces Abstracta's website features like user registration, wish list, shopping cart, product categories, carousels displaying products for exploratory testing.

Exploratory Testing Process

This part focuses on conducting exploratory tests on Abstracta's website by interacting with various features without specific guidance.

Exploratory Testing Procedure

• The process involves interacting with featured products by checking content accuracy, adding products to cart/wish list/comparison list while noting any issues encountered.

• Detailed steps include selecting products for wish list/cart/comparison list and documenting any incidents detected during interaction with site features.

Further Exploration and Incident Reporting

Continuing from previous tests, this section delves into exploring additional functionalities on the website and reporting incidents encountered.

Additional Testing Steps

• Verification of adding products to wish list without guidance is suggested as an additional task beyond defined mission for potential task division recording.

• Selecting more products from featured section for detailed examination including image verification and review presence while maintaining focus on predefined mission.

Incident Detection and Documentation

• Noting discrepancies like incorrect images associated with products for future reporting purposes along with successful product purchase verifications.

• Adding items to comparison list successfully but encountering issues like redirecting errors when selecting certain products from carousels.

Final Testing Phase

Concluding the exploratory tests by examining category-based product additions and addressing issues related to product selection accuracy.

Final Test Procedures

• Detecting inconsistencies in product redirection upon selection leading to incident documentation for further analysis.

• Recording instances where selected items do not correspond correctly or redirect improperly within the website structure.

Completion of Exploratory Tests

Exploratory Testing Process

In this section, the speaker discusses the process of exploratory testing, including the types of tests conducted, incident recording, risk identification, and time allocation during testing sessions.

Types of Tests Conducted

• The speaker outlines the functionalities tested and the specific tests performed on each one to document the coverage of the session.

Incident Recording

• Incidents detected during testing are recorded either directly in the exploratory test session document or in a project tool. Each incident is detailed with steps to reproduce, expected vs. actual results, and evidence.

Risk Identification

• Risks identified if exploratory testing is not conducted include user inability to view products for purchase, confusion due to invalid product content leading to user distrust or purchase disputes, and users unable to perform basic actions for correct purchases.

Time Allocation

• The speaker emphasizes completing missing data such as empty data files used during testing. They also record start and end dates of tests and analyze time spent on actual testing versus reporting issues.

Metrics Generation

• Information from exploratory testing sessions is crucial for generating reports and metrics. This includes functionalities tested, time spent per test, devices used, and incidents reported. These metrics aid in creating various reports for team members and clients.

Metrics Generation from Exploratory Testing

This part delves into generating metrics from exploratory testing sessions to track progress, incidents detected per module/functionality, planned versus executed sessions, and pending tasks.

Progress Tracking Metrics

• Metrics generated include modules/functionalities covered in applications, planned versus executed sessions per functionality/module highlighting progress status.

Incident Detection Metrics

• The number of incidents detected per module/functionality is tracked through metrics derived from exploratory testing sessions.

Graphical Representation

• Data can be visualized through graphs showing information like completed versus pending sessions or incidents detected per module/functionality using bar charts or other graphical formats.

Mapping Sessions in Exploratory Testing

Mapping out application sections/modules covered in different exploratory test sessions aids in identifying areas with frequent incidents while serving as a useful guide for new team members.

Importance of Mapping Sessions

• Creating a map helps visualize which sections/modules were addressed in various test sessions along with areas prone to incidents. It serves as a valuable resource for new team members understanding application functionality.