PumpITup

If you’re not tired of the AI buzz, let’s discuss it in #qakitchen 03! There were ideas for more specific topics, but first, I’d like to explore the broader question: "What is AI’s impact on software QA?" * How to test using AI * How to test software built with AI * How to test software with AI components Also, we’re extending the discussion time to 20+20 minutes again. Welcome anybody open to discussion, don't forget to register on the linked Teams event.

We are planning the next #qakitchen focused on discussion between software QA professionals, 60% discussion guaranteed. Next session will be in the week of 3-7 Feb? Interested into any of below topics? Would like to have a 15 minutes intro for one of the topic? It's a great opportunity for networking and for testing your presentation skills in a friendly environment. Until then, feel free to also join our Discord server at: https://lnkd.in/eVhJ7ZXx

👋 We’re hiring: Software Developer in Test Do you love automating tests and finding smarter solutions? Join our team and work on backend challenges (with a touch of frontend, too). 💡 What we’re looking for: 👉 At least 1 day per week onsite in Prague 👉 Experience with test automation (Kafka, DB, REST/SOAP) 👉 Professional-level English 📍 Sound like you? Check out the details below 👇 Let’s chat and see if we’re a match!

Next #qakitchen scheduled for January 8th, this time we will discuss #ShiftLeft, the why and what can go wrong. This will be a preface to further discussing this in subsequent events because it's a big topic. Nastassia (Nastya) Chaliapina will be the kitchen master this time and introduce the topic. We will give more room for discussion with total 35/60 minutes of the agenda being discussion. Looking forward for your active participation.

Managing infrastructure manually leads to inconsistency, errors, and wasted time. Infrastructure as Code (IaC) solves this by treating infrastructure like software: 🔳 Reproducibility: Code defines the exact state of your infrastructure, so environments are consistent across development, testing, and production. 🔳 Version control: Changes are tracked, reviewed, and reversible, reducing the risk of misconfigurations. 🔳 Automation: Provision and update infrastructure reliably using tools like Terraform, Ansible, or CloudFormation. Manual setups are fragile, hard to scale, and difficult to debug. With IaC, infrastructure becomes more predictable, reliable, and easier to maintain.

Usually people start fighting what is better: #Playwright or #Selenium. So we did the opposite and started bridging both because guess what: both have very similar issues to solve so why not solving them just once: - Scalability - External test results reporting - Auditability etc... See below the proposal of Václav Brož to explain technical details on how we did it. By the way... it's still fully open source.

QA Kitchen is a space for sharing problems and solutions across borders and breaking out of our own bubbles. Each session features a pre-selected topic (case study) presented by a kitchen master, who shares the problem and one possible solution. Participants then contribute their ideas in breakout rooms, ensuring interactivity and maximizing value through shared inspiration. Help us choose the topic for the next session! Note: If you'd like to step up as a kitchen master and deliver a 15-minute presentation on how you tackled one of the listed challenges, feel free to DM Václav Brož. The focus is on sharing ideas, so we don’t expect a highly polished presentation — it’s an opportunity to give back to the community. #qakitchen

🔐 Preventing secret exposure in DevOps pipelines 🔐 Here’s a practical approach: 1. Automated secret scanning: Integrate secret scanning tools directly into the CI/CD pipeline to automatically detect exposed secrets in code, configuration files, and infrastructure templates before they reach production. Look for scanners that handle common secret patterns (like AWS keys or SSH keys) and provide regular updates for new types of tokens. 2. Secret management solutions: Use dedicated secret management tools (such as HashiCorp Vault or AWS Secrets Manager) to securely store and inject secrets into the pipeline without hardcoding them in code. These tools also support version control for secrets, making it easier to roll back to previous configurations if needed. 3. Environment segmentation: For each environment (development, testing, staging, production), set up different credentials and access levels. Segmentation limits the impact of any accidental exposure and ensures that secrets aren’t shared across environments unnecessarily. 4. Access control and auditing: Implement fine-grained access controls and regularly audit access logs to monitor who accessed secrets and when. This step helps identify any unusual patterns early on and minimizes the chance of unauthorized access. #DevOps #SecretsManagement #Security

Automation in IT should be straightforward and practical. We focuse on making business processes and test automation accessible and effective for everyone—from startups to established enterprises. Every IT process has its challenges, but with PumpITup, automation doesn’t have to be one of them. Key products: 🌟 Sixpack: A data management platform designed to simplify synthetic test data creation and usage, preventing data conflicts and keeping tests consistent. 🌟 Pumpo#5: A testing framework that allows easy setup for automated tests, so teams can avoid repetitive manual work. 🌟 Flow100: A process automation tool that takes care of routine tasks across departments. With PumpITup, you get tools that bring clarity and reduce workload. #Automation #PumpITup #Testing #DataManagement