December 8, 2023 by cryan.com

Hello fellow Quality Assurance professionals! Today, I'm excited to share a tool that has significantly streamlined my QA workflow over the past five years: Snagit's Stamp tool. As a seasoned QA professional, I've found that the right tools can make a world of difference in our daily tasks. This week, I'm introducing five custom stamps designed specifically for our QA needs, styled as sleek Apple App buttons.

1. Snagit Stamp Tool: A Brief Overview

Before diving into the custom stamps, let's briefly touch on what the Snagit Stamp tool is. For those unfamiliar, Snagit is a powerful screen capture utility that goes beyond simple screenshots. One of its features, the Stamp tool, allows users to add predefined or custom icons to their screenshots, making annotations quicker and more intuitive.

2. Why Custom Stamps for QA?

In our field, communication clarity is key. Whether we're approving features, flagging issues, or noting minor concerns, our feedback needs to be instant and unmistakable. That's where these custom stamps come in. Designed to be intuitive and eye-catching, they convey our message at a glance.

Click on image to download file.

3. The Five Custom Stamps

• Approved Stamp: This stamp signifies that a feature or section has passed QA testing. It's clean, clear, and gives a green light for progress.
• Approved Green Stamp: Similar to the Approved stamp but in a vibrant green, symbolizing a strong go-ahead.
• Fail Stamp: Use this when something isn't up to par. It's a straightforward, no-miss way to indicate that a feature needs revisiting.
• Fail Red Stamp: The red variant of the Fail stamp, for when you need to emphasize an urgent or significant issue.
• Minor Issues Stamp: Not everything is black or white. This stamp is for those in-between scenarios where minor tweaks are needed.

4. How to Add These Stamps to Your Library

Adding these custom stamps to your Snagit library is easy. Here's how you do it:

Select Your Image: First, drag one of the images to the Snagit icon. (Or select File>Open within Snagit and select one of the images) Save As Stamp: Navigate to the top menu and choose File > Save As Stamp. This action adds your selected image to the 'Custom' section of the Stamp tool.

5. Download the Custom Stamps

I've made these stamps available for you to download and add to your personal stamp library. Download the Stamp Images.

Conclusion

Incorporating these custom Snagit stamps into your QA process can save time, reduce miscommunication, and add a touch of professionalism to your work. I encourage you to download them, try them out, and see the difference they make in your QA workflow.

Stay tuned for more QA tips and tools in future posts!

QA App Buttons for Snagit

December 6, 2023 by cryan.com

Hello fellow Quality Assurance professionals! Today, I'm excited to share a tool that has significantly streamlined my QA workflow over the past five years: Snagit's Stamp tool. As a seasoned QA professional, I've found that the right tools can make a world of difference in our daily tasks. This week, I'm introducing five custom stamps designed specifically for our QA needs, styled as sleek Apple App buttons.

1. Snagit Stamp Tool: A Brief Overview

Before diving into the custom stamps, let's briefly touch on what the Snagit Stamp tool is. For those unfamiliar, Snagit is a powerful screen capture utility that goes beyond simple screenshots. One of its features, the Stamp tool, allows users to add predefined or custom icons to their screenshots, making annotations quicker and more intuitive.

2. Why Custom Stamps for QA?

In our field, communication clarity is key. Whether we're approving features, flagging issues, or noting minor concerns, our feedback needs to be instant and unmistakable. That's where these custom stamps come in. Designed to be intuitive and eye-catching, they convey our message at a glance.

Click on image to download file.

3. The Five Custom Stamps

• Approved Stamp: This stamp signifies that a feature or section has passed QA testing. It's clean, clear, and gives a green light for progress.
• Approved Green Stamp: Similar to the Approved stamp but in a vibrant green, symbolizing a strong go-ahead.
• Fail Stamp: Use this when something isn't up to par. It's a straightforward, no-miss way to indicate that a feature needs revisiting.
• Fail Red Stamp: The red variant of the Fail stamp, for when you need to emphasize an urgent or significant issue.
• Minor Issues Stamp: Not everything is black or white. This stamp is for those in-between scenarios where minor tweaks are needed.

4. How to Add These Stamps to Your Library

Adding these custom stamps to your Snagit library is easy. Here's how you do it:

Select Your Image: First, drag one of the images to the Snagit icon. (Or select File>Open within Snagit and select one of the images) Save As Stamp: Navigate to the top menu and choose File > Save As Stamp. This action adds your selected image to the 'Custom' section of the Stamp tool.

5. Download the Custom Stamps

I've made these stamps available for you to download and add to your personal stamp library. Download the Stamp Images.

Conclusion

Incorporating these custom Snagit stamps into your QA process can save time, reduce miscommunication, and add a touch of professionalism to your work. I encourage you to download them, try them out, and see the difference they make in your QA workflow.

Stay tuned for more QA tips and tools in future posts!

80/20 Pareto Principle in QA

December 5, 2023 by cryan.com

In the ever-evolving field of software testing, the Pareto Principle, commonly known as the 80/20 rule, has emerged as a cornerstone for efficient testing strategies. With a decade of experience in Quality Assurance (QA), I've seen firsthand how this principle can be a game changer in acceptance testing. In this blog, we'll delve into the Pareto Principle and its application in prioritizing test cases for acceptance testing.

Understanding the Pareto Principle

The Pareto Principle, initially observed by Vilfredo Pareto, states that roughly 80% of effects come from 20% of causes. In the context of QA, this translates to the idea that a majority of software issues are often due to a small portion of all possible causes.

Application in Acceptance Testing

Acceptance testing is a critical phase in software development where we verify whether the system meets the business requirements. It's the final checkpoint before the software reaches the end user, making the selection of test cases crucial. Here's how the Pareto Principle aids in this process:

1. Identifying Critical Test Cases

Not all test cases are created equal. Some have a higher impact on the overall system functionality than others. By applying the 80/20 rule, we focus on identifying the 20% of test cases that are likely to uncover 80% of the most crucial bugs. These often include core functionalities and features most frequently used by end-users.

2. Resource Optimization

In any project, resources ? be it time, manpower, or tools ? are always limited. The Pareto Principle helps in allocating these resources effectively. By targeting the most significant test cases first, teams ensure that the majority of potential defects are caught early, saving time and effort in the long run.

3. Risk Management

Acceptance testing is not just about finding bugs but also about risk management. The 80/20 rule aids in identifying areas with the highest risk and potential impact on the system's performance and stability. Focusing on these areas ensures that critical issues are addressed before the product release.

4. Enhancing Test Coverage

While it may seem counterintuitive, concentrating on the most impactful 20% of test cases can lead to better test coverage. This approach ensures that testing is more focused and comprehensive in areas that matter the most.

5. Continuous Improvement

The Pareto Principle also plays a vital role in the continuous improvement of the testing process. By regularly analyzing which test cases fall into the critical 20%, QA teams can adjust and evolve their testing strategies to stay aligned with changing user requirements and system functionalities.

Conclusion

Incorporating the Pareto Principle in acceptance testing is not just a strategy but a mindset shift. It encourages QA professionals to think critically about the value and impact of each test case. By focusing on the most significant test cases, teams can ensure that they are efficiently utilizing their resources while maintaining high standards of quality and reliability in the software they deliver.

Remember, the goal of applying the Pareto Principle in acceptance testing is to maximize efficiency without compromising on quality. It's about working smarter, not harder, to achieve the best possible outcomes in the realm of software quality assurance.

February 1998 Commercials

December 4, 2023 by cryan.com

In February 1998, a younger version of myself was immersed in the world of cable TV, diligently recording a myriad of shows. At the time, my intentions were unclear, perhaps driven by a simple desire to capture a slice of television history. Fast forward twenty-six years, and curiosity led me back to these old recordings. To my delight, I uncovered a treasure trove of classic 1990s commercials, a nostalgic journey through a bygone era of advertising. These commercials, once mere intervals in my viewing experience, now stand as captivating time capsules, offering a glimpse into the vibrant culture and trends of the 90s.

Check out:

• In Living Color Season 2 Introduction
• 1998 Pontiac Trans Am Commercial
• Cadillac Catera Commercial - Introduced just two years earlier.
• Fremont Ford - Wow check out those 1998 prices.
• US Army Reserve - Be all you can be
• TCI Cable - Why would you want Satellite service?
• Crest Toothpaste - How about the basic Toothpaste tube design?
• Adidas - Featuring Antoine Walker just 2 years into his NBA career.
• The Grand Central Sauna & Hot Tub Co. - This popular San Francisco spot closed because of the pandemic.

Watch the Video

Rudolph the Red Nose Reindeer

December 3, 2023 by cryan.com

Rudolph the Red-Nosed Reindeer came up in a conversation this weekend at a Santa Claus event. I thought it would be good to learn more about this character.

Rudolph the Red-Nosed Reindeer is a beloved Christmas character with a fascinating history and some fun facts:

1. Created for a Department Store: Rudolph was created in 1939 by Robert L. May for Montgomery Ward, a department store, as part of a Christmas promotion.

2. Rudolph Almost Had a Different Name: May considered naming Rudolph "Rollo" or "Reginald" before settling on Rudolph.

3. The Song Came Later: The famous song "Rudolph the Red-Nosed Reindeer" was written by Johnny Marks, May's brother-in-law, in 1949, a decade after the character was created.

4. Gene Autry Made the Song Famous: The song gained immense popularity when Gene Autry recorded it in 1949. It became a huge hit, eventually selling millions of copies.

5. Rudolph Wasn't Part of Original Reindeer: In the original "A Visit from St.?Nicholas" (also known as "The Night Before Christmas"), Rudolph isn't mentioned. He was added to the reindeer team later.

6. First Appeared in a Booklet: Rudolph first appeared in a booklet written by May and distributed by Montgomery Ward.

7. A TV Special Popularized Rudolph Further: The 1964 stop-motion TV special "Rudolph the Red-Nosed Reindeer" helped popularize Rudolph even more and has become a holiday staple.

8. Rudolph's Red Nose is Scientifically Explained: Some scientists have explained that a reindeer's nose turning red in extreme cold could be due to the dense network of blood vessels in their noses, a theory often linked in fun to Rudolph's famous trait.

Rudolph's story of overcoming obstacles and his bright red nose has made him a symbol of Christmas and a character loved by generations.

HalfStaff.org

December 2, 2023 by cryan.com

HalfStaff.org is a unique and insightful website dedicated to providing information about American flag half-staff notifications. Here's a closer look at what the site offers:

Understanding HalfStaff.org

1. Timely Notifications: The website plays a crucial role in disseminating information about when and why the American flag is flown at half-staff. For instance, recently, the website notified its audience to fly the flag at half-staff from November 25 to November 29, 2023, as a mark of respect.

2. Tributes to Notable Figures: The half-staff notifications often pay tribute to significant individuals. A recent example is the proclamation on the death of Rosalynn Carter, the former First Lady of the United States. The website detailed her contributions and the presidential order to fly the flag at half-staff in her honor.

3. Educational Resource: Beyond notifications, HalfStaff.org serves as an educational resource, informing the public about the protocol and significance of flying the flag at half-staff. This practice is a powerful symbol of national mourning and respect.

4. Integration with Websites and Blogs: The site offers a widget that can be integrated into blogs or websites, allowing for the wider dissemination of half-staff notifications. This feature ensures that the information reaches a broader audience, promoting national unity and awareness during times of mourning.

Website Description

https://halfstaff.org/

Expanding Polygons Beyond the Default in Keynote

December 1, 2023 by cryan.com

Hello, Mac enthusiasts! This week, we're diving into a neat trick within MacOS that many users overlook. By default, when you draw a polygon in most MacOS applications, it comes with five sides. However, did you know you can easily expand this number to create more complex shapes? Let's explore how to expand a polygon to have up to 11 sides by simply using a green dot.

1. Starting with the Basics:
   • First, open the application where you want to draw your polygon (such as Pages, or Keynote).
   • Select the shape tool and choose the polygon shape.
2. Understanding the Default Setting:
   • By default, the polygon appears with five sides.
   • Notice the green dot on one of the vertices of the polygon ? this is your key to customization.
3. Expanding the Polygon:
   • Click and hold the green dot. As you start dragging it, you'll see the number of sides increase.
   • Slowly drag the dot around the center of the polygon, and watch as the sides increase up to 11.
4. Customization Tips:
   • Remember that as you add more sides, the shape gradually becomes more circular.
   • Experiment with different numbers of sides for various projects ? whether it's for graphic design, presentations, or just for fun.
5. Applications and Creativity:
   • This feature is particularly useful in design projects where you need polygons that are not commonly available.
   • Combine it with other tools like color fill, border adjustments, and rotation to create unique graphics.

Conclusion

Expanding the sides of a polygon from the default five to up to eleven opens up a new world of design possibilities on your Mac. It's a simple yet powerful way to add flair to your documents and presentations. As always, the key is to experiment and find what works best for your creative needs. Stay tuned for more tips and tricks next week!

cURL in Python

November 30, 2023 by cryan.com

As a QA professional, I've encountered various tools and methodologies that enhance testing processes. Among these, Unix cURL stands out for its utility in handling network requests. In this blog, I'll delve into how we can leverage cURL within Python to streamline our testing and automation tasks.

What is cURL?

cURL, short for 'Client for URLs', is a command-line tool used to transfer data to or from a server. It supports a variety of protocols, including HTTP, HTTPS, FTP, and more. While cURL is inherently a Unix-based tool, its functionality is crucial for testing APIs, web applications, and automating network requests.

Why Use cURL in Python?

Python's extensive libraries like requests are commonly used for handling HTTP requests. However, cURL offers a different approach with its command-line driven method, which is sometimes more flexible and powerful, especially when dealing with complex scenarios or when reproducing requests copied from browsers' developer tools.

Integrating cURL with Python

There are several ways to integrate cURL commands into Python, with the most common method being the use of subprocess module. Here's a basic example:

import subprocess

def curl_command(url):
    command = f"curl {url}"
    process = subprocess.Popen(command, stdout=subprocess.PIPE, shell=True)
    output, error = process.communicate()
    if error:
        print(f"Error: {error}")
    else:
        return output.decode('utf-8')

# Example Usage
response = curl_command("https://api.example.com/data")
print(response)

This script uses subprocess.Popen to execute a cURL command and fetch data from a given URL. It's a straightforward way to integrate cURL's capabilities into a Python script.

Handling Complex cURL Commands

For more complex scenarios, like sending data, handling headers, or dealing with authentication, the cURL command string can be modified accordingly. For instance:

def complex_curl_command(url, data, headers):
    command = f"curl -X POST -d '{data}' -H '{headers}' {url}"
    # Rest of the code remains similar

Advantages and Limitations

Advantages: 1. Direct Transfer from Browsers: cURL commands can often be copied as-is from browsers' developer tools, which is handy for reproducing and automating specific requests. 2. Support for Multiple Protocols: cURL's versatility across different protocols makes it a powerful tool in a QA's arsenal.

Limitations: 1. Security Concerns: Running shell commands from within Python can pose security risks, especially when dealing with untrusted input. 2. Complexity: For simple HTTP requests, using Python libraries like requests is more straightforward and Pythonic.

Conclusion

Integrating Unix cURL with Python scripts provides a robust method for handling complex network requests. It's particularly useful for QA professionals looking to automate and test applications with specific network interactions. However, it's essential to weigh its benefits against potential security risks and complexity.

For those interested in exploring further, I recommend experimenting with different cURL options and understanding how they translate into the Python context. Happy testing!

Snagit Signature Stamp

November 29, 2023 by cryan.com

What makes the Stamp tool remarkable is its simplicity and effectiveness. You can choose from a range of pre-made stamps or create your own. Here's where it gets exciting: incorporating your signature into screenshots. (Putting your signature on your testing!)

I recently experimented with adding my signature, crafted in the elegant Jamesville Script font, as a custom stamp in Snagit. The process was straightforward. I first created a signature in Jamesville Script, saved it as an image file, and then imported it into Snagit as a custom stamp. Now, with a few clicks, I can add a personal touch to my screenshots, whether for professional documentation or personal projects.

This feature is particularly useful for QA professionals like myself. We often need to sign off on captured images or mark them as reviewed. Adding a signature stamp not only streamlines this process but also adds a layer of personalization and authenticity.

In conclusion, Snagit's Stamp tool opens up a realm of possibilities for creative and practical applications. The ability to add a personal signature stamp, like the one in Jamesville Script, elevates your screen captures from mere images to personalized documents, reflecting both professionalism and a hint of personal style.

Wearing the Red Coat in Software Engineering

November 28, 2023 by cryan.com

Introduction

In the world of software engineering, the Quality Assurance (QA) team often plays a critical, albeit understated, role. Drawing an analogy from Ozan Varol's insightful book, "Think Like a Rocket Scientist," we can liken the role of QA professionals to wearing the "Red Coat," a concept rooted in red teaming strategies. Here, I share insights from my decade-long experience in QA and explore how this role acts as the red team in the engineering world, ensuring the robustness and reliability of software products.

The Red Coat Analogy in QA

In "Think Like a Rocket Scientist," Varol describes how red teams play the adversary, aiming to uncover weaknesses in the blue team's strategies. In software engineering, QA professionals wear the Red Coat, symbolizing their role as the first line of defense against potential failures. We deep dive into the depths of software, much like a red team, to identify vulnerabilities, bugs, and areas of improvement that could otherwise lead to significant issues post-deployment.

QA: The Unsung Heroes in Engineering

QA teams often operate in the background, meticulously testing and retesting software to ensure its quality. Our work is crucial yet frequently goes unnoticed ? until something goes wrong. By rigorously challenging the assumptions and work of the development team (akin to the blue team), we prevent potential crises, safeguard user experience, and uphold the software's integrity.

The Proactive Approach of QA

The essence of wearing the Red Coat in QA is not just about finding faults but adopting a proactive approach. We don't just look for what is broken; we anticipate where and how software might fail. This forward-thinking mindset enables us to contribute significantly to the planning and development phases, ensuring that potential issues are addressed before they become real problems.

Collaboration and Challenge

Effective QA is not about working in opposition to the development team but in collaboration with them. We challenge assumptions not to criticize but to strengthen the final product. This collaborative tension is essential for innovation and quality, much like the dynamic between the red and blue teams described by Varol.

Tools and Techniques in QA Red Teaming

In our arsenal are various tools and techniques ? from automated testing frameworks to manual exploratory testing. We simulate adverse conditions, stress test systems, and think like the end-user, constantly asking, "What could possible go wrong?" Our goal is to ensure that when the software faces real-world challenges, it performs seamlessly.

Conclusion: Embracing the Red Coat Philosophy

As QA professionals, embracing the Red Coat philosophy means standing out and being the critical voice that ensures software excellence. Our role is vital in catching the unseen, questioning the status quo, and pushing for higher standards. In the grand scheme of software engineering, we are not just testers; we are guardians of quality, playing a pivotal role in the successful launch and operation of software products.

In conclusion, the next time you use a software application that works flawlessly, remember the Red Coats behind the scenes ? the QA teams who have tirelessly worked to make your digital experience seamless and efficient.