Call for Speakers opens in November - Pre-register for updates

AutomationSTAR

Test Automation Conference Europe

AutomationSTAR

Speak on stage at AutomationSTAR

The AutomationSTAR Call for Speakers is open until January 31st – have you sent in your submission yet?

This year’s conference takes place in Vienna, 9-10 October. We are looking for test automation engineers, developers, architects, QA, and team leaders to take to the AutomationSTAR stage, and share your experiences with an incredible audience: a community keen to learn & improve their own projects.

Remember, this is not a general testing conference; it is completely focused on test automation. Nobody is doing test automation exactly the way you are, so share your own personal journey. How will you create engaging discussions, facilitate active learning, and inspire others? Your knowledge can make a big impact.

see call for speakers

It’s Europe’s biggest test automation event

Last year’s conference was bigger than we ever anticipated, with over 450 attendees from all around Europe coming together for two days totally dedicated to all things test automation. We’re scaling up even more for 2024, with more learnings, more networking opportunities, and even more fun!

The programme team, chaired by Ryan Volker (Germany); along with Janna Loeffler (USA), Geosley Andrades (India) will dedicate their time to creating a truly epic line-up of speakers for the programme. Check off your goal of speaking at a conference by being part of the biggest test automation event in Europe.

Submission types

Here’s what the programme team is looking for:

Half-Day Tutorials: 3 hour expert masterclasses. Popular tutorials can be large (possibly up to 100 people). Exercises need to be easy to explain, understand and perform to be practical.

Workshops are 90-minute sessions. We prefer sessions that engage the class and have substantial workshop or hands-on content. These sessions are intended to be educational and experiential.

Track Talks are 45-minute sessions with 30 minutes of presentation/talk, followed by 15 minutes of Q&A and audience discussion

All submissions should be relevant to test automation in software development and testing. Our attendees have requested more technical content, so this is a key focus for 2024. Check out all the details for the Call for Speakers and see what topics will help you form a great submission.

start submission

Efficient Software Testing in 2023: Trends, AI Collaboration and Tools

In the rapidly evolving field of software development, efficient software testing has emerged as a critical component in the quality assurance process. As we navigate through 2023, several prominent trends are shaping the landscape of software testing, with artificial intelligence (AI) taking center stage. We’ll delve into the current state of software testing, focusing on the latest trends, the increasing collaboration with AI, and the most innovative tools.

Test Automation Trends

Being aware of QA trends is critical. By staying up to date on the latest developments and practices in quality assurance, professionals can adapt their approaches to meet evolving industry standards. Based on the World Quality Report by Capgemini & Sogeti, and The State of Testing by PractiTest, popular QA trends currently include:

  • Test Automation: Increasing adoption for efficient and comprehensive testing.
  • Shift-Left and Shift-Right Testing: Early testing and testing in production environments for improved quality.
  • Agile and DevOps Practices: Integrating testing in Agile workflows and embracing DevOps principles.
  • AI and Machine Learning: Utilizing AI/ML for intelligent test automation and predictive analytics.
  • Continuous Testing: Seamless and comprehensive testing throughout the software delivery process.
  • Cloud-Based Testing: Leveraging cloud computing for scalable and cost-effective testing environments.
  • Robotic Process Automation (RPA): Automating repetitive testing tasks and processes to enhance efficiency and accuracy.

QA and AI Collaboration

It’s no secret that AI is transforming our lives, and ChatGPT’s collaboration can automate a substantial portion of QA routines. We’ve compiled a list of helpful prompts to streamline your testing process and save time.

Test Case Generation

Here are some prompts to assist in generating test cases using AI:

“Generate test cases for {function_name} considering all possible input scenarios.”
“Create a set of boundary test cases for {module_name} to validate edge cases.”
“Design test cases to verify the integration of {component_A} and {component_B}.”
“Construct test cases for {feature_name} to validate its response under different conditions.”
“Produce test cases to assess the performance of {API_name} with varying loads.”
“Develop test cases to check the error handling and exceptions in {class_name}.”

Feel free to modify these prompts to better suit your specific testing requirements.

Example

We asked for a test case to be generated for a registration process with specific fields: First Name, Last Name, Address, and City.

AI provided a test case named “User Registration” for the scenario where a user attempts to register with valid inputs for the required fields. The test case includes preconditions, test steps, test data, and the expected result.

Test Code Generation

In the same way, you can create automated tests for web pages and their test scenarios.

To enhance the relevance of the generated code, it is important to leverage your expertise in test automation. We recommend studying the tutorial and using appropriate tools, such as JetBrains Aqua, to write your tests that provide tangible examples of automatically generating UI tests for web pages.

Progressive Tools

Using advanced tools for test automation is essential because they enhance efficiency by streamlining the testing process and providing features like test code generation and code insights. These tools also promote scalability, allowing for the management and execution of many tests as complex software systems grow.

UI Test Automation

To efficiently explore a web page and identify available locators:
Open the desired page.
iInteract with the web elements by clicking on them.
Add the generated code to your Page Object.

This approach allows for a systematic and effective way of discovering and incorporating locators into your test automation framework.

Code Insights

To efficiently search for available locators based on substrings or attributes, you can leverage autocompletion functionality provided by the JetBrains Aqua IDE or plugin.

In cases where you don’t remember the location to which a locator leads, you can navigate seamlessly between the web element and the corresponding source code. This allows you to quickly locate and understand the context of the locator, making it easier to maintain and modify your test automation scripts. This flexibility facilitates efficient troubleshooting and enhances the overall development experience.

Test Case As A Code

The Test Case As A Code approach is valuable for integrating manual testing and test automation. Creating test cases alongside the code enables close collaboration between manual testers and automation engineers. New test cases can be easily attached to their corresponding automation tests and removed once automated. Synchronization between manual and automated tests to ensure consistency and accuracy is a challenge that does not need to be addressed. Additionally, leveraging version control systems (VCS) offers additional benefits such as versioning, collaboration, and traceability, enhancing the overall test development process.

Stay Tuned

The industry’s rapid development is exciting, and we are proud to be a part of this growth. We have created JetBrains Aqua, an IDE specifically designed for test automation. With Aqua, we aim to provide a cutting-edge solution that empowers testers and QA professionals. Stay tuned for more updates as we continue to innovate and contribute to the dynamic test automation field!

Author

Alexandra Psheborovskaya, (Alex Pshe)

Alexandra works as a SDET and a Product Manager on the Aqua team at JetBrains. She shares her knowledge with others by mentoring QA colleagues, such as in Women In Tech programs, supporting women in testing as a Women Techmakers Ambassador, hosting a quality podcast, and speaking at professional conferences.

JetBrains is an EXPO Gold partner at AutomationSTAR 2023, join us in Berlin

How to Choose the Right Test Automation Tool for Your Testing Needs

Navigating the vast landscape of test automation tools and platforms can be a daunting task.
With a plethora of options available, each boasting unique features and capabilities, how do you
make the right choice for your specific testing needs? This article aims to guide you through the
process, ensuring you select a tool that aligns perfectly with your requirements.

1. Understanding You Requirements


Before diving into the sea of tools, it’s crucial to have a clear understanding of your testing
needs:

  • Application Type: Start by identifying the nature of your application. Are you testing a
    sleek web application, a mobile app that needs to function seamlessly across devices, or
    perhaps a traditional desktop application? The type of application you’re working with
    can significantly influence your tool choice.
  • Platform Compatibility: In today’s diverse tech ecosystem, compatibility is key. If your
    application is designed to run on multiple operating systems, you’ll need a tool that
    supports cross-platform testing. On the other hand, if your focus is solely on a specific
    OS, ensure the tool you choose excels in that environment.
  • Integration Essentials: Modern development and testing often involve a suite of tools
    working in tandem. Think about your existing tech stack. Does your test automation tool
    need to play well with CI/CD pipelines for seamless deployments? Should it integrate
    effortlessly with your version control system to track changes? Pinpointing these
    integration needs upfront can save you a lot of hassle down the road.

2. Open Source vs. Commercial

When it comes to test automation tools, there’s often a debate between open-source and
commercial options. Both have their merits, and the best choice largely depends on your
specific needs and constraints. Let’s dive deeper:

  • The Allure of Open Source: Tools like Selenium have made a significant mark in the
    testing world, and for good reason. Open-source tools provide flexibility, allowing you to
    tailor them to your exact requirements. And yes, they’re free! However, it’s essential to
    note that “free” doesn’t always mean zero cost. Open-source tools might require a
    steeper learning curve, more setup time, and ongoing maintenance. This also has an
    associated cost to develop a well suited test framework to manage automation capability
    effectively
  • The Premium Touch of Commercial Tools: On the flip side, commercial tools often
    come with a price tag, but they offer a polished experience in return. Think of them as an
    all-inclusive package. They might boast advanced features not found in open-source
    counterparts, offer dedicated customer support to address your queries, and provide
    comprehensive documentation to ease your journey. For teams that need specific
    functionalities or prefer a more guided experience, commercial tools can be worth the
    investment.
  • Budget Considerations: While open-source tools don’t have licensing fees, remember
    to factor in potential costs associated with setup, maintenance, and training along with
    automation resources and SDET engineers to design, develop and maintain automation
    framework. Commercial tools, on the other hand, might have upfront or recurring costs,
    but they could offer a more streamlined experience, reducing long-term expenses.
    Return of investment on automation is essential with respect to time to market. A well
    verse business case is the key to success.
  • Feature Exploration: Always keep an eye on the feature set. While open-source tools
    offer a lot of flexibility, commercial tools might come with unique features that can
    significantly boost your testing efficiency.

3. Aligning with Your Team’s Skill Set

Every team is unique, with its own set of strengths, experiences, and preferences. When
choosing a test automation tool, it’s essential to consider the capabilities and comfort level of
your team members. Here’s how:

Scripting Proficiency: Dive into the technical depth of your team. Are they well-versed
in scripting languages, or do they lean more towards a no-code or low-code approach?
Some automation tools demand a strong coding background, allowing for intricate test
scenarios and customizations. In contrast, others provide a script-less environment,
where tests can be designed using simple drag-and-drop actions or natural language.
Choose a tool that complements your team’s expertise.

User Experience Matters: In the world of software, a tool’s user interface can make or
break the user experience. A well-designed, intuitive interface can significantly
accelerate the testing process, allowing team members to focus on creating robust tests
rather than navigating a complex tool. Moreover, a user-friendly tool can flatten the
learning curve, enabling even newcomers to get up to speed quickly.

4. Scalability and Performance

In the dynamic world of software development, projects evolve. What starts as a small
application can quickly grow into a large-scale platform with multiple features and functionalities.
As such, your test automation tool should be ready to scale up alongside your project. Here’s
what to consider:

  • Parallel Execution: Time is of the essence, especially when you have a vast suite of tests to run. Does your chosen tool support parallel execution? This feature allows multiple tests to run simultaneously, drastically reducing the overall testing time. It’s like having multiple testers working on different parts of your application at the same time, ensuring swift feedback and faster releases.
  • Embracing the Cloud: The cloud has revolutionized the way we think about scalability. With cloud support, your testing platform can easily adapt to increased demands without the hassles of manual infrastructure management. Whether you’re running a handful of tests today or thousands tomorrow, a cloud-based platform ensures consistent performance, flexibility, and accessibility from anywhere.
  • Maintenance Overheads: Test automation scripts and frameworks require ongoing maintenance. Changes in the application under test can break existing scripts, requiring updates. Maintaining a large number of fragile scripts can be time-consuming and frustrating.

5. Community and Support

A vibrant community and dedicated support can make the difference between a smooth
testing experience and a challenging one. Here’s why:

  • Forums and Documentation: Imagine encountering a tricky issue at an odd hour. Where do you turn? Active forums can be a lifesaver, offering insights, solutions, and shared experiences from fellow users worldwide. Additionally, comprehensive documentation and tutorials act as a roadmap, guiding you through the tool’s features, best practices, and troubleshooting steps. They’re like having a user manual tailored to your needs, ensuring you get the most out of your tool.
  • Vendor Support: While community support is fantastic, there are times when you need expert assistance. This is especially true for commercial tools. A responsive vendor support team can address your queries, provide technical assistance, and even offer insights into upcoming features and improvements. It’s like having a dedicated team backing your testing efforts, ensuring you never feel stuck.

6. Integration Capabilities

In today’s interconnected tech landscape, no tool is an island. Your test automation tool, no
matter how powerful, needs to integrate with the other tools in your ecosystem. The integration
ensures a fluid workflow, enhancing efficiency and productivity. Here’s what to look for:

  • CI/CD Integration: Continuous Integration and Continuous Deployment (CI/CD) have become the backbone of modern software development. They ensure that code changes are automatically tested and deployed, leading to faster releases and improved quality. Your test automation tool should be a natural fit within this pipeline, triggering tests as code changes and providing timely feedback to developers. It’s like having a vigilant sentinel that ensures every code change meets the quality standards.
  • Plugin Support: The world of software is vast, and sometimes, you need specialized functionalities that aren’t part of the core tool. That’s where plugins or add-ons come into play. They extend the capabilities of your tool, allowing it to adapt to specific needs. Whether it’s integrating with a unique reporting tool, supporting a specific test framework, or adding a new feature, plugins ensure your tool remains versatile and tailored to your requirements.

7. Review and Feedback

User reviews, feedback, and firsthand experiences can provide a wealth of insights, helping you make an informed decision. Here’s how to tap into these resources:

  • User Reviews and Feedback: There’s a saying that experience is the best teacher, and in the world of software tools, this couldn’t be truer. Dive into user reviews and feedback to understand the strengths and weaknesses of a tool from a real-world perspective. It’s like having a candid conversation with a fellow user, getting the inside scoop on what to expect.
  • Case Studies: Beyond individual reviews, case studies offer a deeper dive into how companies have utilized the tool. They showcase real-world scenarios, implementation strategies, and the outcomes achieved. By exploring case studies, you can gain insights into how the tool performs in diverse environments, the challenges encountered, and the solutions adopted. It’s a window into the tool’s practical application in various settings.
  • Trial Before Commitment: Many tools offer trial versions, allowing you to test the waters before making a commitment. This hands-on experience is invaluable. It lets you explore the tool’s features, gauge its compatibility with your needs, and assess its performance in your specific environment. Think of it as a test drive, ensuring the tool feels right before you invest time and resources.

8. Future-Proofing

In the fast-paced world of technology, what’s cutting-edge today might become obsolete
tomorrow. As such, when selecting a test automation tool, it’s essential to look beyond its
current capabilities and consider its potential to evolve with the times. Here’s how to ensure
your tool is future-ready:

  • Regular Updates and Upgrades: A tool that’s regularly updated reflects a commitment to excellence and adaptability. Dive into the tool’s update history and its roadmap for the future. Frequent updates not only mean that bugs and issues are addressed promptly but also that the tool is continually enhanced with new features and capabilities. It’s like choosing a car that not only runs smoothly now but is also equipped for the roads of tomorrow.
  • Adaptability to New Trends: The tech industry is known for its innovations, from emerging programming languages to novel testing methodologies. Your chosen tool should have the flexibility to adapt to these changes. Whether it’s supporting a new browser, integrating with a trending CI/CD platform, or accommodating a fresh testing approach, the tool’s adaptability ensures you’re always at the forefront of testing excellence
  • Data Management: Test data management is crucial for effective testing. Ensuring that test data remains relevant and up-to-date can be a complex task, particularly in large and complex testing environments.
  • Test Automation Framework: a well-designed test automation framework can streamline the testing process, enhance test coverage, and contribute to the overall quality and reliability of software applications, making it an essential component of modern software development and testing practices.
  • Test Automation Strategy: Elevate your software development with a smart test automation strategy. Speed up testing, cut costs, and deliver top-quality software faster. It’s the competitive advantage your team needs.

Conclusion

Choosing the right test automation tool or platform is a critical decision that can influence the
success of your testing efforts. By considering the factors mentioned above and aligning them
with your specific needs, you can make an informed choice that not only meets your current
requirements but also scales with your future endeavors.

Author

Solitera Team

Solitera Test Automation (SoliteraTA) aims to make the software testing more accessible and efficient for organisations. SoliteraTA is all in one solution for automating web, mobile and desktop applications. It help teams to improve efficiency and effectiveness of their testing processes, and ultimately deliver higher-quality software products with better ROIs.
Solution provides a library of pre-built operations in a straightforward BDD style format for effortless and speedy creation of automated tests. This library eliminates the need for users to possess knowledge of programming languages or complex testing frameworks. The overall solution design facilitates the swift and efficient development of automation capabilities.

Solitera are a Exhibitors at AutomationSTAR 20-21 Nov. 2023. Join us in Berlin.

The Importance of Code Quality: Production vs. Test

Code quality is a topic of prime importance in any software development cycle. It influences not only code functionality but also its maintainability, scalability, and long-term viability. Unfortunately, while we hope it is done for production code, it is often overlooked for test code. As a QA Manager, it’s crucial to understand and advocate for the necessity of high-quality code in both production and testing. Before discussing test code quality, let’s differentiate between test scripts and test code; it’s a crucial consideration.

Test Scripts vs. Test Code: The Distinction

We typically create Test scripts in one of two ways: using record-and-playback tools, then converting the results into scripts; or writing scripts line by line, action by action, as independent tests with limited or no reusability. While scripts seem simple to create and may be quick to deploy, they typically lack flexibility and are brittle, making them susceptible to breaking when things change. This can lead to regression gaps with abandoned scripts and other undesirable results. Test scripts are most suitable for simple, static workflows.

Conversely, test code involves writing code for test automation, ranging from unit tests to API tests to end-to-end tests. This approach often utilizes SDETs (Software Development Engineers in Test) or developers who know object-oriented principles, page object models, and data-driven testing principles. Typically needing fewer resources, it offers superior flexibility, robustness, and efficiency, making it ideal for complex projects with longer lifecycles or systems integral to an organization.

Why Does Code Quality Matter?

Code quality is the cornerstone of any reliable, robust, and efficient software system. Poor code quality can lead to bugs, security vulnerabilities, performance issues, and even system failures. On the other hand, high-quality code addresses these concerns while being easier to read, maintain, and extend, reducing the time and resources needed for debugging and shortening release cycles. High-quality code is good.

While the importance of production code quality is evident, test code quality is often overlooked, if not wholly ignored. We know what can happen with poor production code. Similarly, poor test code can lead to reduced regression testing, missed requirements, or even false positives or negatives, which are notoriously difficult to find. Good test code quality helps resolve these issues in the same way good production code quality helps resolve problems.

Remember, testing is your primary defense against software bugs and defects.

What’s More Important, Production Code Quality Or Test Code Quality?

Let me preface this with my experience across many large enterprise organizations: Code quality is challenging at the best of times, even with organizations having the best intent. And as large projects start running into delays, code quality is often an early victim.

A woman in an orange/red shirt thinking about a puzzling questionBack to the question: both production and test code quality are critical, but test code quality is more important than production code quality. Why, you ask?

Let’s answer that with another question. Which is better: a system with the best code ever but does not work as expected or a poorly written, unmaintainable system that does everything expected?  

We all agree that a system that works as expected is preferred, regardless of the quality of its code. 

The nature of development means bugs; the issue is how quickly you identify and fix them. The better you test, the quicker you find bugs. And the quicker you find bugs, the faster you fix them. So good testing is critical, and the more maintainable and sustainable your tests are, the quicker they can adapt as your system changes, letting you identify bugs sooner.  

Since testing ensures the quality of your production system, and production code quality does not guarantee functionality, test code quality is critical to the success of your test system and, ultimately, your production system, which needs to work, regardless of its code quality. 

Summary 

This article underscores the importance of code quality for both software development and testing. It further differentiates between automated test scripts and test code, accentuating the latter’s superiority. We also see that test code quality can compensate for deficiencies in production code quality while protecting against bugs, explaining how test code quality adds as much if not more, value than production code quality.   

Are you ready to challenge your views and see test code quality in a new light?

Author 

Kim Filiatrault Founder and President

Kim has been in the IT industry for over 35 years, most of it in highly technical areas including generative technologies and test automation. In 2005, Kim specialized in Insurtech and helped many enterprise customers implement large projects. More recently, his company released CenterTest, its new test automation technology, based on his decades of test automation and generative technologies expertise and they have started helping companies revolutionize the way they test.

When not working, Kim enjoys off-roading with his Jeep, going to the UT Longhorns Football games, serving his local communities, and traveling. 

Kimputing are an Exhibitor Sponsor at AutomationSTAR 20-21 Nov. 2023 in Berlin 

Kim Filiatrault

Speaker Interview: Geosley Andrades on his Eureka Moment, Advice for Testers & More

AutomationSTAR 2023 speaker Geosley Andrades shares his thoughts on test automation practices, and gives an insight into what you can expect at his talk, ‘Unlock New Possibilities in Test Automation with ChatGPT’.

1. How did you get into testing?

I embarked on my journey in the field of testing under somewhat serendipitous circumstances. Initially, I entered the realm of IT as a .NET developer. However, the year 2008 brought with it a challenging wave of economic recession, which prompted me to make a strategic career choice. It was during this pivotal moment that I decided to delve into the world of testing. Over the years, I have not only embraced this profession wholeheartedly but have also found immense passion and fulfillment in the journey it has offered me

2. What was your Test Automation Eureka moment?

As a relative newcomer to the field with just one year of experience, I was entrusted with the task of building my first test automation framework from scratch. To my astonishment, this framework not only benefited my team but was also adopted as the preferred choice across other teams within my organization. This transformative experience ignited my deep passion for test automation and set me on a course of continuous growth and innovation in the field.

3. If you had the power to change one widely accepted practice in testing, what would it be, and why do you think it needs to change?

I would advocate for a shift from primarily UI testing towards a more comprehensive approach, encompassing deeper layers like APIs, databases, and integrated systems. This change is necessary because, in many organizations, testing often remains superficial, focusing only on the UI, leaving underlying issues undiscovered until later stages.

4. Some argue that traditional testing methods are obsolete in the age of Automation. Do you believe there’s still value in manual testing, or is it a dying practice?

There is undoubtedly enduring value in human-driven exploratory testing, and I firmly believe that it is far from a dying practice. While automation tools have advanced significantly and streamlined many testing processes, they lack the critical element of human judgment, intuition, and creativity. Unlike tools, humans possess the cognitive capacity to evaluate, recognize patterns, make nuanced decisions, think critically, interpret results, observe subtle issues, and adapt to evolving scenarios. As a result, human-driven exploratory testing remains a vital component of the testing landscape, complementing Automation and AI-driven techniques. It ensures the discovery of complex and context-specific defects that can be challenging for tools to identify.

5. What can attendees expect to gain from your presentation or workshop at the AutomationSTAR conference?

As AI’s prominence continues to grow, it’s a consensus that AI won’t replace testers, but testers who harness AI’s power definitely will. In my presentation, we will embark on a journey to uncover innovative approaches through which ChatGPT (Generative AI) can empower testers and augment their skill set. Furthermore, I will delve into the significance of educating ourselves about this Generative AI technology and adopting it as an invaluable tool, reframing it from a perceived threat. The moment has arrived for us to embrace AI and redirect our focus toward the facets of our roles that deliver the most value.

6. What’s the biggest message you have for AutomationSTAR Attendees?

With its dedicated focus on Automation, AutomationSTAR offers a unique opportunity for everyone in the testing community. Featuring an array of automation-related topics presented by world-class speakers, the conference promises a wealth of knowledge and networking opportunities. As a speaker myself, I’m eagerly anticipating not only sharing insights but also learning and connecting with the automation community. I encourage all of you to participate in this celebration of our craft and leverage this event to propel your test automation careers to new heights. See you there!

It’s your last chance to get tickets to the AutomationSTAR Conference in Berlin, 20-21 November. The enthusiasm from the community is incredible – tutorials are sold out, and our new Conference Only tickets are being snapped up! Get your tickets now.