Roman Leca

Struggling to Find Reliable QA News? 📰 I often faced the challenge of searching multiple platforms to find interesting and high-quality articles about QA. Realizing that many others might be experiencing the same issue, I decided to create my own Telegram channel – 𝑻𝒆𝒔𝒕𝑻𝒆𝒄𝒉 𝑪𝒉𝒓𝒐𝒏𝒊𝒄𝒍𝒆𝒔. Over the past two months, I’ve dedicated significant time to curating content from reputable sources. Each article on the channel comes with a concise summary and a quiz to help you remember the key points. 📝 If you find yourself spending too much time searching for good QA news, join 𝑻𝒆𝒔𝒕𝑻𝒆𝒄𝒉 𝑪𝒉𝒓𝒐𝒏𝒊𝒄𝒍𝒆𝒔 for your one-stop source of the latest updates, trends, and insights. I would be thrilled to have you on board! 🚀 🔗 Join 𝑻𝒆𝒔𝒕𝑻𝒆𝒄𝒉 𝑪𝒉𝒓𝒐𝒏𝒊𝒄𝒍𝒆𝒔 on Telegram https://lnkd.in/dyKerEjr #QA #SoftwareTesting #QualityAssurance #TestTechChronicles #StayInformed #IndustryUpdates #JoinTheCommunity

1

In software development, many companies believe that the role of a Quality Assurance (QA) engineer begins at the end of the project. This is a common mistake that can lead to major problems and unexpected costs. Having a QA engineer involved from the start ensures that every phase is tested and that the project stays on the right track from day one. For example, if you're working on an ERP system without a QA engineer from the beginning, you might discover critical issues after the development is finished, such as errors in accounting or data integration. This leads to project delays and increased costs. However, if a QA engineer had been involved from the start, these issues could have been identified early, saving both time and effort. In short: Having a QA engineer from day one is not a luxury; it’s a necessary investment to ensure the product's quality and reduce errors and costs. #qa #qualityassurance #testing #software #SoftwareTesting #Mohammad_Albaba #quality #SoftwareDevelopment #ERP #projectmanagement #QAEngineer

8

Dear LinkedIn members! 👋 In my journey as a QA Engineer, I’ve found that being well-prepared for interviews is key to success. To help others in their preparation, I’m starting a weekly series where I’ll share common interview questions along with concise explanations. 🚀 QA Engineer Interview Questions Series - Week 1 🚀 ❓ This Week’s Question: What are the most common challenges faced in test automation? 🕯 Pro Tip: Always plan for scalability and maintainability when building your automation framework. It will save you time and effort in the long run! 💡 Answer: 1. Tool Selection: Choosing the right tool that fits the project requirements can be challenging, especially with the vast options available. 2. Maintenance: Automated test scripts require regular updates and maintenance as the application evolves. 3. Test Data Management: Managing and preparing test data for automation can be time-consuming. 4. Initial Investment: Setting up an automation framework requires a significant initial investment in terms of time and resources. 💬 Feel free to drop your answers in the comments! Let’s learn together and grow as a community. ✨ 📢 Stay tuned for more insights in the coming weeks! #InterviewPrep #QAStrategy #TestingChallenges #AutomationTesting #CareerGrowth #InterviewQuestions

77

12 Comentarii

𝗪𝗲𝗲𝗸 𝟯, 𝗹𝗲𝘀𝘀𝗼𝗻 𝟱 at GoIT România's QA Manual course! 🚀 𝘗𝘢𝘳𝘵 𝘈: What is 𝗧𝗲𝘀𝘁 𝗠𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁: Test Management involves the preparation and planning of tests, ensuring objectivity by having different individuals perform the testing. This can include testers, clients, developers, and other team members. Levels of Independence in Testing (from the author, in ascending order): 1. Developer tests own code. 2. Code review by the developer, an independent tester, or another team member. 3. Independent testing team within the company reporting to project management. 4. Independent testers from the client or users with specialized skills (e.g., usability, security). 5. Independent testing team outside the software development company ("outsourcing/outstaff"). 𝗔𝗱𝘃𝗮𝗻𝘁𝗮𝗴𝗲𝘀 𝗼𝗳 𝗜𝗻𝗱𝗲𝗽𝗲𝗻𝗱𝗲𝗻𝘁 𝗧𝗲𝘀𝘁𝗶𝗻𝗴: 1. Unbiased testers can identify different bugs than developers. 2. Independent testers can validate implicit assumptions made during system specification and implementation. Independent testing in software development has its drawbacks that every Test Manager should be aware of. Some of these 𝗱𝗶𝘀𝗮𝗱𝘃𝗮𝗻𝘁𝗮𝗴𝗲𝘀 include: - Potential communication breakdown if testers and developers are too isolated. - Vulnerability due to insufficient resources, leading to delays in releases. - Risk of developers relying too heavily on testers to fix product quality issues. - Possibility of independent testers lacking essential information for thorough testing. 𝗧𝗵𝗲 𝗧𝗲𝘀𝘁 𝗠𝗮𝗻𝗮𝗴𝗲𝗿 plays a crucial role in overseeing the testing process and managing testing activities. Responsibilities of a Test Manager may involve: - Developing and updating the testing policy and strategy. - Planning test activities based on objectives, risks, and resources. - Creating and revising test plans. - Coordinating with project managers, product owners, and stakeholders. - Leading test analysis, design, implementation, and execution. - Monitoring test progress, results, and meeting exit criteria. - Implementing relevant indicators and enhancing the expertise of the test team. In any test project, 𝘁𝗲𝘀𝘁 𝗽𝗹𝗮𝗻𝗻𝗶𝗻𝗴 stands out as the most critical task for a 𝗧𝗲𝘀𝘁 𝗠𝗮𝗻𝗮𝗴𝗲𝗿. Understanding these challenges and responsibilities is key to ensuring successful testing outcomes. 𝗧𝗲𝘀𝘁 𝗽𝗹𝗮𝗻𝗻𝗶𝗻𝗴 is a crucial aspect of ensuring successful software testing. This involves defining scope, objectives, and risks, as well as integrating testing activities within the software life cycle. Decisions on what to test, how to test, and resource allocation are key components. Additionally, scheduling, selecting monitoring parameters, budgeting resources, and defining documentation details are all part of effective test planning.  #TestPlanning #SoftwareTesting #QualityAssurance

3

Here is just a small piece of information for all QA in my connections: Whenever the Interviewer asks you the following: What are the different forms of testing you have performed? Don't Answer these: 1. I have done functional and non-functional testing 2. I have performed smoke, sanity, and regression testing. 3. I have performed both manual and automation testing Rather answer like a pro: 1. I have performed smoke, sanity, and regression testing as a part of functional testing and performed performance, load, and stress testing as non-functional testing, moreover as a QA I have come across multiple forms of manual testing such as Cross-Browser testing, Accessibility testing, etc(that you have performed). 2. If a person has worked as an Automation QA, do mention all the sorts of automation testing you have done such as:- I have started my automation testing journey with Selenium Java combination then implemented TestNG and used Maven as a build automation tool, and currently as our organization focuses on latest technology so I am learning the importance of Playwright and Cypress. There are more ways of answering different sets of questions the interviewer asks you and you can get better by learning more about testing and the QA domain but the most important point for a QA is to express their answers in a more descriptive way not to impress the interviewer but for yourself to bring out the self-confidence in this domain #testing #interviewquestions #qaanalyst

492

38 Comentarii

How to find your first QA job if you are Switcher? Part 2. (You can find Part 1 and the first 3 points below on my feed) 4. Believe in yourself This is one of the most useful recommendations I received from two more experienced mentors. If you don't believe in yourself, why should recruiters and your future colleagues? Practices that can help to increase your self-belief: -write a list of your personal achievements -write a list of your achievements from previously work or study -look in the mirror every day and repeat at least 3-5 times: "I deserve the company I want. I deserve the salary I want. My skills and I are enough to achieve what I want"... Hug yourself after practice 5. Identify who your target audience is Try to analyse yourself from the outside and try to imagine which company might hire you. Where would you fit in? Describe this company. For example, a company is looking for someone more experienced than you, but invite you to the tech interview. Companies that might be your target audience: -have a strong mentoring programme within the company -are willing to invest time in you and help you develop your skills -value your strong soft skills and proactivity 6. Be open to any opportunities Any practice experience is useful for your next steps. Even a few months of commercial experience in any field will make you stand out among other candidates and can teach you useful things. If you're starting your journey in the QA field, be open to exploring new opportunities. Don’t miss out on internships, training sessions, tech meetups, or conferences. 7. Pet projects Practice on a realised products and attach the documentation to your CV. In my opinion, 5-10 good examples will be enough. 8. Improve your LinkedIn page Try to write about your first steps, share information that can be useful for people who have the same goals as you. Don't be discouraged if you don't get a lot of feedback from the Network, because even 1 like on your post is better than nothing, and for 1 more than you had a week ago 😅 Your posts are about communication and showing the way you think. Share it with the world, because your posts can work for you even months later when a recruiter to go to your page from your CV. Creating a great LinkedIn profile is an opportunity to communicate with recruiters without dialogue. Don't miss this chance to demonstrate why you are a strong professional – even without work experience. Some links that might be useful. Implement what resonates with you: https://lnkd.in/ej6wCFTz  https://lnkd.in/eSWD6G86 Remember – you are already is a part of QA community, just without job 😉

32

Hello LinkedIn Community! I'm seeking insights from fellow QA professionals on a topic that's crucial for effective software testing. In your experience, how many words should the "Expected Results" section of an ideal test case contain? - Should it be concise and to the point? - Or should it be detailed and comprehensive? Your input and experiences would be greatly appreciated! #SoftwareTesting #QATesting #TestCases #QualityAssurance #AutomationTesting #ManualTesting

5

2 Comentarii

Testing is often undervalued, but it's time to change that narrative.⏰👨‍💻Here are some thoughts about QA from our cofounder Ivan Barajas ⤵ #testing #softwaretesting #softwarequality #softwarequalityassurance #qualityassurance

4

Major Update for Everyone! Those who have already enrolled in my Package: Become SDET & Future SDET Manager + 950+ Q&A Bank Have already received access for latest E-Book "Become Master of Test Automation Frameworks" Note: Refresh the links and you will get access! Now if you haven't already, then do enroll in this package if your goal is to become an SDET. What it covers? Automation Framework E-Book: 1. Test automation framework design challenges? 2. Types of Development Techniques in Agile Methodologies 3. Automation Framework Architecture 4. How Abstraction Works in Test Automation Frameworks? 5. What test types should be automated as Priority for companies/organizations which are starting out from scratch? 6. Important Interview Questions for Frameworks 7. Design Patterns Strategy Pattern Factory Pattern Factory Pattern in Creating WebDriver Instance: Page Object Model Breakdown (for beginners) PAGE Object Model Description 8. Advanced Page Object Model 9. Test Data Management 10. SOLID 11. Functional Testing and Types 12. Non Functional Testing and Types 13. Test Planning, Setup for Functional and APIs 14. Automation Feasibility from Manual to Automation For Package Details read here: https://lnkd.in/gusymgFi As it's month end, I have lowered the prices! All the best and keep learning :) #japneetsachdeva

40

1 Comentariu

This is what happening right now…. Blindly asking for all skill set and end up with writing test cases in excel sheet…. Worst part is even if we went through whole interview process, we will be getting an answer as position is on hold… if they are willing to keep the position in hold what is the need of keeping the interviews? ##justasking ##manualtestingmatters

3

One of the most common question during the interview for QA position is - What is your "favorite bug". Here are some interesting examples of bugs that could occur in an e-commerce platform: 1. The Infinite Discount Bug: A pricing calculation error allowed customers to apply the same coupon code multiple times, potentially reducing the price to zero or even negative values. 2. The Midnight Order Glitch: Orders placed exactly at midnight were assigned to the wrong day, causing issues with inventory management and delivery scheduling. 3. The Currency Conversion Catastrophe: A decimal point error in currency conversion led to items being sold for a fraction of their intended price in certain countries. 4. The Phantom Inventory Bug: Cancelled orders didn't properly return items to inventory, leading to "out of stock" messages for products that were actually available. 5. The Review Time-Travel Issue: A timezone handling error allowed users to post product reviews with future dates, making them appear at the top of the review list indefinitely. 6. The Cart Abandonment Amnesia: User's abandoned carts were being cleared unexpectedly, losing potential sales and causing frustration for returning customers. 7. The Free Shipping Fiasco: A logic error in the shipping calculator offered free shipping on extremely heavy items, potentially costing the company significant amounts in shipping fees. 8. The Search Engine Snafu: A bug in the search algorithm caused results to be sorted by price from highest to lowest instead of relevance, affecting user experience and potentially sales. 9. The Mobile Checkout Maze: A responsive design flaw made the "Confirm Purchase" button unreachable on certain mobile devices, preventing order completion. 10. The Infinite Loading Loop: A caching issue caused product pages to enter an endless loading state for users with certain browser extensions enabled.

14

An important resource

2

QA Advice of the day: Testing in different time zones Do you work on an internationally used application? Does it show some dates and times, for example in some reporting feature? If yes, then you might want to check how those dates are shown for users in different time zones. If it is an application installed on client's premise you should probably test it with different time zones set on the web and database server as well. Just saying. I write about QA stuff. Today, just like any other day I give free QA advice. Follow Uros Simic and visit my blog (link in profile) for more advice like this.

19

👩‍💻 Anastasiia Kopachynska, Manual QA Engineer at Sombra, spills the tea on the common mistakes QA engineers make when trying to optimize API testing with Postman. From forgetting how to handle dynamic variables to accidentally sending requests into the void, these little oopsies can really throw a wrench in your testing flow. Want to avoid the chaos? Learn how to automate token retrieval without breaking a sweat, manage headers like a boss, and generate random data that doesn’t feel… too random. 👉 Plus, we’ll show you how to keep your scripts organized (no, naming it “final_final_v2” won’t help), execute requests in the right order, and keep your test cases clean. Because cluttered databases? Not on our watch. 😏 Read the tips below 👇🏻

20

1 Comentariu

QA Expert Seeking New Opportunities: 3 Years of Software Testing Excellence 🚀 Hello, LinkedIn community! 👋 I'm a passionate Quality Assurance professional on the hunt for exciting new challenges. My QA Journey: • Started with manual testing, mastering: - Bug identification 🐛 - Test case development 📝 - Usability assessment 🧐 As technology evolved, so did my expertise. I've expanded my toolkit to include: • API Testing: - REST Assured - Postman • Web and Mobile Automation: - Selenium - Codeceptjs Results? 40% faster test execution and 25% increase in testing coverage. 📊 Why QA Matters: As a parent, I know the critical importance of reliable technology. From educational apps to banking software, user trust is paramount. 🛡️ What I'm Seeking: Opportunities with companies that value both technical proficiency and user-centric development. Let's create exceptional software solutions together! Open to remote QA positions and career advice. Share your opportunities or insights below! Discussion Starters: 1. Which emerging QA tools excite you most? 2. How has remote work impacted your QA team's efficiency? 3. Any tips for balancing a tech career with parenting? Let's learn and grow together! Your thoughts could spark innovation in our community. 🌱💻 #QualityAssurance #SoftwareTesting #OpenToWork

3

Real Challenges for QA Engineer: My Daily Reality Hello, LinkedIn community! 👋 I want to share what sometimes makes my job a real challenge—not to complain but to collaborate with you all to find better solutions. 1. Juggling Time and Quality — When projects race towards deadlines at full speed, I often have to make quick decisions about how deep to dive into testing details. It's always a tough choice that impacts the final product quality. Solution: Implementing agile methodologies can be extremely beneficial. We can better allocate time for thorough testing and adjustments by breaking down projects into smaller, manageable sprints. Additionally, using automated testing tools for repetitive tasks frees more time for complex test scenarios. 2. Vague Requirements—Ah, those moments when you start testing and the specifications raise more questions than they answer. This forces me to seek additional information, which can delay the process. Solution: I've found proactive communication and regular alignment meetings with the project team are crucial. Creating a detailed checklist of requirements before testing begins ensures that all parties understand and agree on what needs to be done. 3. Synergy with the Development Team — If there are communication gaps, the outcome can be far from perfect. These moments are frustrating, but they also show how important our cohesion is. Solution: Establishing a CI/CD pipeline can enhance collaboration. It allows for quicker iterations and immediate feedback, reducing misunderstandings and fostering a team environment where everyone is aligned on the project goals. 4. The Pressure of Compromises — Sometimes, it feels like everyone expects a "green light" from me, even when I see clear issues. It puts me in a difficult moral dilemma. Solution: Developing a clear risk management plan helps in making informed decisions. When faced with the pressure to overlook issues, having predefined criteria for critical bugs and a communication plan to present these findings to stakeholders can help mitigate the need for uncomfortable compromises. If you also work in testing, you've probably faced similar challenges. What are your strategies for dealing with them? I would appreciate any advice or techniques that have helped you. Thank you for being here, and I look forward to your stories and advice! 

3

1 Comentariu

Hi friend testers, the new version of CYPRESS-AJV-SCHEMA-VALIDATOR v1.2.0 is out!!! 🚀🚀🚀 It includes two MAJOR new features: - Full integration with bahmutov/cy-api and filiphric/cypress-plugin-api to display JSON violations directly in their UI outputs. 🤯 - A new configuration option to disable schema validation in your tests. 🤩 With this release, you can save minutes, or even hours, when debugging JSON schema errors during your API testing. Read all about it in the blog post: "CYPRESS-AJV-SCHEMA-VALIDATOR v1.2.0: Boost Debugging Skills from Vigilante to Superhero with Advanced Schema Error Insights!" 🦸 https://lnkd.in/gynvXsxh You can also see the attached video of how it looks when integrated with both the cy.api() plugins. Cypress.io & JSON Schema

108

6 Comentarii