Yulia Romanova

👩‍💻 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 Comment

🔺 Situation for QA #7. 🔺 Your program has a requirement: ‘The value in the “Sum” field must be calculated as the sum of the values ​​from fields A and B.’ Which test case would be more correct? Answers: A. In field A, enter the value 5, and in field B, enter the value 2. Click on the “Calculate” button. Expected result: The value 7 is displayed in the Amount field. B. Enter a symbol in field A, and another symbol in field B. Click on the “Calculate” button. Expected result: a message indicating that incorrect data was entered. C. Enter a symbol in field A, and any value in field B. Click on the “Calculate” button. Expected result: a message that the data in field B is incorrect. D. Enter values ​​in fields A and B. Expected result: the value in the “Amount” field should be calculated as the sum of the values ​​​​from fields A and B.

1

𝗪𝗲𝗲𝗸 𝟯, 𝗹𝗲𝘀𝘀𝗼𝗻 𝟱 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

🔍 Overview of Key Testing Techniques: Black Box, White Box, Grey Box 🔍 Curious to learn more about different testing techniques? Let's explore the basics of black box, white box, and grey box testing with some examples and the roles responsible for each: 1. **Black Box Testing**: Imagine you're testing a web application's login functionality. In black box testing, you focus solely on the inputs (username and password) and outputs (successful login or error message). Testers or Quality Assurance (QA) professionals typically perform black box testing, focusing on the application's behavior without needing knowledge of its internal structure. 2. **White Box Testing**: Now, let's consider the same login functionality, but from a white box testing perspective. With access to the source code, developers and QA engineers collaborate to design test cases that ensure all code paths are executed correctly. Developers may write unit tests to validate individual components, while QA engineers perform integration testing to verify the interaction between components. 3. **Grey Box Testing**: In grey box testing, testers have partial knowledge of the internal workings of the application. For example, they may know the database structure used for storing user credentials. Testers and QA engineers work together to design tests that verify both the functionality (black box) and the integration with the database (white box), ensuring a more comprehensive testing approach. Understanding when and how to apply each technique is key to designing effective testing strategies. 🛠️ #SoftwareTesting #QualityAssurance #TestingTechniques #manualqa #qualityassurance #softwaretesting #teamcollaboration #softwareengineering #techindustry #codereview #testcases #linkedinnetworking #projectmanagement

1

💡 3 years ago, I started my QA journey. Key milestones: 📍 Started with manual testing 📍 Learned test automation 📍 Mastered CI/CD integration 📍 Led end-to-end testing projects Biggest lessons: 1. Quality is everyone's responsibility 2. Communication > Tools 3. Early testing saves time To junior QAs: focus on understanding the business logic first, tools second. #QualityAssurance #CareerGrowth #SoftwareTesting

5

1 Comment

#Playwright or #Selenium – which tool fits your web testing needs? 🤔 Our latest article, written by QA engineers Amir Temimovic, Kerim Hadzibegović, and Nedim Lisica, dives into why Playwright is emerging as the new industry standard. From seamless browser support to enhanced speed, find out why it’s a game-changer for automated testing. Read the full comparison here: https://lnkd.in/djJ8UM7V #qa #testing #automation #tech #plusplusmag #klikaus

12

Starting a QA Testing Course for Beginners! If you want to start a career in IT/SQA, this course is perfect for you! I'll cover the basics of QA testing with hands-on learning. Interested? Drop a comment or message Muhammad Shariq Naeem and I'll add you to the group! #QATesting #SoftwareTesting #CareerInTech #LetsGrowTogether

46

41 Comments

Unlock the secrets to acing your next junior-level Technical QA interview with our latest Medium article, 'Mastering Technical QA Interviews. Explore crucial topics such as SDLC, STLC, test types, and more. This guide is designed to help budding QA professionals build a solid foundation and shine in their interviews. Dive in now and get equipped to impress! 🚀 #JuniorQA #TechInterviews #SoftwareTesting"

20

1 Comment

A new post from my occasional newsletter 🥂 #qa #softwaretesting #softwaretesting101 #qualityassurance #networking #article #exploratory #testing #weeklyarticle #agile #agiletesting #qaresume

2

Bugs Are a Team Issue, Not Just QA’s Responsibility! 🐛🔄 Let’s stop treating QA like the only line of defense against bugs. In reality, quality is everyone’s job – from the first line of code to the final product. 👨‍💻 Developers: Ensure clean, maintainable code.   📚 Business Analysts & Product Teams: Provide clear and detailed requirements.   🔍 QA: Test rigorously, but they’re not the last stop for quality. 🤝 The Entire Team: Work together to deliver quality. When we all take ownership of the product’s quality, the result is stronger, more reliable software. Quality is built, not tested. Let’s make it a team priority! How does your team ensure quality throughout the process? #QualityIsATeamEffort #SoftwareDevelopment #Testing #QA #Collaboration #Agile

4

🔺 Test for QA #25. 🔺 What are the types of integration testing? Answers: A. Full, partial, selective, corrective, progressive B. Minimum, maximum and balanced C. The integration testing stage is usually not divided into types D. Bottom-up, top-down, hybrid method, big bang

10

2 Comments

🔺 Test for QA #26. 🔺 What is the main criterion for acceptance testing? Answers: A. Test coverage reached 100% B. Positive code review report C. Test plan fulfillment 100% D. Customer requirements fulfilled E. Test Strategy compliance

2

1 Comment

QA Knowledge: Most easiest and commonly asked interview question. Question: 𝗪𝗵𝗮𝘁 𝗶𝘀 𝘁𝗵𝗲 𝘀𝗶𝗴𝗻𝗶𝗳𝗶𝗰𝗮𝗻𝗰𝗲 𝗼𝗳 𝘁𝗵𝗲 `𝗽𝘂𝗯𝗹𝗶𝗰 𝘀𝘁𝗮𝘁𝗶𝗰 𝘃𝗼𝗶𝗱 𝗺𝗮𝗶𝗻(𝗦𝘁𝗿𝗶𝗻𝗴[] 𝗮𝗿𝗴𝘀)` 𝗺𝗲𝘁𝗵𝗼𝗱 𝗶𝗻 𝗝𝗮𝘃𝗮, 𝗮𝗻𝗱 𝘄𝗵𝘆 𝗶𝘀 𝗲𝗮𝗰𝗵 𝗽𝗮𝗿𝘁 𝗼𝗳 𝘁𝗵𝗶𝘀 𝗺𝗲𝘁𝗵𝗼𝗱 𝗻𝗲𝗰𝗲𝘀𝘀𝗮𝗿𝘆? A:nswer: The `public static void main(String[] args)` method is the entry point of any Java application. Here's a breakdown of its components: 𝗽𝘂𝗯𝗹𝗶𝗰: The public keyword is an access modifier that allows the main method to be accessible from anywhere, including outside the class. This is crucial because the Java Virtual Machine (JVM) needs to call this method to start the program. Without public, the JVM would not be able to access the main method, and the program would not run. 𝘀𝘁𝗮𝘁𝗶𝗰: The static keyword means that the main method belongs to the class rather than any instance of the class. This allows the JVM to invoke the main method without needing to create an instance of the class. Since the program starts before any objects are created, the main method must be static. 𝘃𝗼𝗶𝗱: The void keyword indicates that the main method does not return any value. The main method's primary purpose is to start the execution of the program, so it doesn't need to return data to the JVM. 𝗺𝗮𝗶𝗻: `main` is the name of the method, and it is a standard method name that the JVM looks for as the entry point of the program. If the method is named something else, the JVM won't recognize it as the starting point, and the program won't run. 𝗦𝘁𝗿𝗶𝗻𝗴[] 𝗮𝗿𝗴𝘀: `String[] args` is an array of String objects that stores any command-line arguments passed to the program when it is executed. This allows the program to accept and process input directly from the command line, making it more flexible and dynamic. **In summary, each part of the public static void main(String[] args) method is essential for the JVM to locate, access, and execute the starting point of a Java application.

19