Polina Naumenko

🔺 Situation for QA #3 🔺 Today is release day. But according to the law of meanness, you found a bug in the product: If you open the application at 6:00 via IE8, it will take three times longer to load. You know that none of your clients use IE8, and they mostly work from 10 am. Your actions? Answers: A. The release needs to be shifted. A bug is a bug. B. The bug is too rare - I won’t do anything with it at all. C. I’ll create a task for correction and put it in the backlog. D. I will inform the QA Lead about this so that he can make a decision about the release.

2

🔍 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

Sometimes what happened in your head had to be written in somewhere, so the track or memories can traced. Just posted my very first Medium 'bout how to fastest way to do assertion but not the best practice of implementation. Here is the link: https://lnkd.in/gtizFf9F Very open to know your thoughts!

17

✅ Steps to Make the QA Process Smoother 🚀 Understand the Requirements Properly Ensure that all requirements are fully understood. Without clear understanding, it is impossible to effectively test all scenarios, and major requirements might be missed. After understanding the requirements, start working on documentation. Create a comprehensive test plan that lists down the entire process. 🚀 Assign Tasks Based on Team Member Skills Allocate tasks according to the skills of each team member to ensure efficiency and effectiveness. 🚀 Create Test Cases Using Black Box Techniques Develop test cases following black box testing techniques such as equivalence partitioning and boundary value analysis. 🚀 Set Clear Testing Timelines Define clear timelines for the testing process to keep everything on track. 🚀 Select Testing Types According to Time Choose the appropriate types of testing based on the available time to maximize efficiency. 🚀 Bug Reporting Try to make a bug report as clear as possible with all proper headings and screenshots. 🚀 Establish Clear Communication Channels Maintain clear communication channels within the team and with stakeholders to ensure everyone is on the same page. 🚀 Collaboration with Developers on Bug Fixing Work collaboratively with developers on bug fixing to ensure timely resolution. 🚀 Continuous Feedback and Improvement Collect continuous feedback and act on it to improve the process. Conduct retrospective meetings at the end of projects to learn lessons and improve for future projects. The pattern that I personally follow to make the testing process smooth. Share your experience in comments also. 😊 #SoftwareTesting #QualityAssurance #ContinuousTesting #AgileTesting #BugReporting #TestPlan

16

1 komentarz

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

🔺 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

A Complete QA BOOK

9

🎓 Excited to share that I've completed the EG Workshop on QA Processes & Best Practices, led by QA Manager Piotr Wilkowski🚀 Throughout the workshop, I gained valuable insights into optimizing quality assurance processes and implementing best practices to enhance product quality. A big thank you to Piotr for his expertise and guidance! Looking forward to applying these learnings in my work and contributing to our team's success. 😊 #ManualTesting #AutomationTesting #Selenium #Appium #MobileAppTesting #Functionize #PerformanceTesting #EGWorkshop

54

I want to share my impressions, while they are still fresh, from participating in the Heisenbug – QA conference 2024 Spring !) This was the first such large conference in my specialty and I barely had time to write down all the interesting things I heard 😁 I was especially impressed by the reports: - Svetlana Sherstobitova about high-performance plugs and what you need to pay attention to when creating them; - Dmitrii Tuchs about creating his own extensions, which inspired me to write my first extensions, very informative; - Oleg Chaplashkin about cross-cutting logging and the use of LUA tests;  - Alexandra Naumova about the first steps in load testing and about the scenarios that are necessary to check the system load (I can already see how I can apply this in a working project); - Alexey Ivanov about rendering problems, clearly, to the point and very interesting; - Maria Palagina talked about the architecture of the project, learned a lot of new things, including about push and pull architecture; - Vyacheslav Dubynin, as always, was inimitable with his report about the brain and everything connected with it (and even managed to talk a little about neural networks); - Arsen Gumin about data quality made me think and reconsider our view of what we operate on the project; - Dmitry Kuznetsov about gaps in test coverage, this report was a revelation for me, especially about tree nodes and how to split requirements!

23

4 komentarze

Are you ready? Picture this: you're about to dive into something new, and the path ahead is a bit foggy. You keep hearing that little voice saying, "Wait until you're totally prepared." But here's the thing I've learned from my journey into QA engineering: waiting for the perfect moment is a trap. When I jumped into QA, I wasn't 100% sure if I was ready. But you know what? The secret to success isn't about starting when you feel completely prepared; it's about having the guts to start even when you don't. This goes for anything in life. Stop waiting for the "perfect" moment. Just go for it and create your own perfect moment by taking that first step. You got this!

3

2 komentarze

🌟 Embracing the Fast Growth of AI Technologies: Why Manual QA Remains Crucial 🌟 Periodically, I am in the circle of colleagues (QA manual) and increasingly I hear fears that technology will quickly replace specialists. Indeed, in the rapidly evolving world of artificial intelligence, we are constantly pushing the boundaries of innovation and functionality. But with so many features and changes being developed and implemented at an unprecedented rate, it becomes imperative to ensure that these solutions are not only cutting-edge, but also reliable and user-friendly. This is where manual quality assurance (QA) plays a key role. 🤔💭 I thought about this question and decided to share with you my thoughts on why manual QA is necessary for a project, regardless of the tools you use or automated tests: 👩‍💻Human Perspective: While automated tests are excellent for consistency and speed, they lack the human intuition and empathy needed to evaluate user experience. Manual QA testers put themselves in the shoes of real users, ensuring that our AI solutions are practical, intuitive, and accessible. 🛸Flexibility and Adaptability: Fast growing projects often involve complex and dynamic features. Manual testers can quickly adapt to new changes and features, exploring them in ways that automated scripts cannot. This flexibility is crucial for identifying unexpected issues and edge cases. 🔍Exploratory Testing: AI technologies bring new, unique challenges that are often unforeseen. Manual QA allows for exploratory testing, where testers can creatively probe and uncover hidden defects that automated tests might miss. ⏳Real-time Feedback: Manual testers provide immediate and qualitative feedback, essential for rapid iteration and refinement. Their insights/reported bugs help developers understand the practical implications of their code and make necessary adjustments swiftly. 📊Validation of Automated Tests: Manual QA acts as a validation layer for automated tests. It ensures that automated testing tools are functioning correctly and that their results are accurate and meaningful. 💪In summary, as we continue to innovate and integrate advanced AI features, maintaining a robust manual QA process is vital. It ensures that our products not only perform well but also provide a seamless and delightful user experience. 

6

QA isn't just a role- it's pathway for evolution. Picture this: Several decades ago, testing was closely intertwined with development. Developers need to test their own code and certified it afterwards experiencing a "instinct regarding the quality of the code". Result: steep production errors, retarded deployment, client disappointment, and so on. Having witnessed all of this, management decided to add the QA stage as a layer between development and production. Some dev's have been requested to donned the QA hat. There could be a mix of them doing this willingly and obtrusively! Those who performed it freely began to appreciate the role and eventually became specialist in their field, establishing an era of 'Dedicated testers'. This era keeps on going. Others who were coerced began spreading unfavorable thoughts about the character. This profession, like any other, has both advantages and disadvantages. The well-known aphorism "It can only get better" roughly translates to "It can't get any worse." It is for those who perceive this area as an opportunity to better get to the next evolution. #QualityAssurance #AStoryofEvolution #TestingEra

12

🔺 Test for QA #5. 🔺 Which type of security test or tools include the process of exploiting software vulnerabilities? Answers: A. Vulnerability assessments B. Static code analysis C. Penetration testing D. Vulnerability scanning

1

The 1st step of making a progress in your QA career is choosing your niche & committing to it. There is a fair "burden" of research & decision making you must take, but I can help you bear it, we're all friends here. 😉 Why A/B testing? Because it s i m p l y m a k e s s e n s e! 🤯 If you were to decorate a home, you'd cater it to the needs of those about to live there, not randomly. If you were to improve a website, you'd adjust it for its actual users. How to do that bullet-proof way? Being driven by data. 💡 How A/B testing works -simply- it compares 2 (or more) versions of the website: the current & an improved one, in any aspect (changes are directed by CRO wizards, using the neuromarketing & other magic 🧙‍♂️). You split the traffic, half of the users see the original, half of them the new version you've created & that's getting tracked. After a period of time, you make an informed decision (by data analyzing) on how the changes have impacted the users & then implement them into the website itself if successful. I cannot emphasize "informed decision" enough. We do things strategically here. 🤓 There is no guessing anymore (you've done that in working test ideas out & conducting them). You stop doing things that might work, you do what you know will work & in such way build your client's business up! 🚀 This is such a rewarding process for both the client & the CRO agency providing the services. Now, why QA in A/B testing? What makes it even more alluring than QA in general? 👀 1. In my personal opinion, the beauty of IT is being dynamic. I cannot do same things over & over & over... again.  In the CRO world, "dynamic" is a weak word! We are adrenaline junkies. This goes fast!!!💥 Multiple tests per day. Different parts of website hit/psychological triggers/aspects you must take to make it as perfect (visually & functionally) as you can/problems that might occur. Your long-term project is your client's roadmap. There you work continuously & slowly. 2. Also, if you're anything like me, you love to think broadly of QA. It's not just a bug-hunt, it's trying to make a damn strong & pretty piece of software. You come up with different improvement points, communicate those with CRO experts you cooperate with, make decisions together. 3. You can & you must learn from everyone. If you want to be at the top of your game, you will learn from optimizers (understand psychology of the users, their goals/needs/fears), data analysts, developers (as soon as I could, I've made a website myself - to walk their walk, to have a whole new level of appreciation & to know what's (not)possible), designers, etc. You're swimming in the ocean of information & you absorb it all like a sponge. 🏊‍♂️ For my jack-of-all-trades people, this is Utopia. 🌞 Conclusion of this post - come to the dark side, we have cookies. 😼 Jokes aside, if I've managed to spark your interest & helped you in choosing which way to go, then my day is made. 🤗 #QASpecialist

8

4 komentarze