SDLC/AGILE/PROJECT AND FRAMEWORK QUESTIONS

Question 1

What would you say, when cannot answer interview question?

Answer 1

To be honest I researched it. But I don’t remember it right now. That’s why I don’t want to say anything wrong. But I will check it out right after the interview.

Question 2

What is regression testing and how do you run it in your project? How many test cases are there and how often do you perform regression testing? How long your regression suite runs?

Answer 2

Regression testing is a key part of checking if software still works well after changes. We do this in different situations, like fixing bugs to make sure the problem is solved without creating new ones, adding new features without messing up existing ones, modifying existing features without causing unexpected issues, and fixing performance problems to keep everything stable. In our project, we have around 500 test cases, taking about 3-4 hours, with 75%-80% automated. We release updates every other sprint in our agile process. Automation involves tagging scenarios like @Regression in Cucumber and running them through the Regression runner class using Jenkins. I also handle manual tests and do ad hoc testing. After testing, I analyze results, find reasons for failures (like environment or application issues), and retest to confirm. If it’s an app issue, I reproduce the bug, check against requirements, and log it in Jira with details like severity, priority, steps to reproduce, and screenshots.

Question 3

Tell us one challenge while running the regression suite?

Answer 3

We don’t really face challenges running the regression suite because I always try to maintain my regression suite periodically, but sometimes it’s because of the server, or the system we can get some unexpected errors like synchronization issues.

Question 4

What is smoke testing and how do you run it in your project? How many test cases are there and how often do you perform smoke testing?

Answer 4

Smoke testing is a crucial phase in software testing that focuses on checking the basic functionality and stability of software build. In our project, we run smoke testing by deploying the build to the QA environment and verifying critical functionali-ties. If successful, the build continues to detailed testing; else, it’s rejected or reverted. We’ve start the smoke test process using Jenkins, a web-based tool. Our smoke test includes around 15 to 20 test cases that cover crucial features of the software. Jenkins triggers the smoke test automatically for each code change, providing quick feedback within minutes. we perform smoke testing every time there’s a code push. This make sure always checking and quickly find problems, helping to develop efficiently and solve issues on time.

Question 5

What is Automation Testing? What are the benefits of Automation Testing?

Answer 5

Automation testing is when special tools run tests on software. It has benefits, like faster feedback and faster results, making the development process more efficient. Although there are higher costs at the start, it saves money in the long run by reducing the need for fixes after release. Automation testing also improves efficiency, it needs less observation and covers more features. The tests can be reused, making assessment easy and reducing testing time and costs.

Question 6

What type of tests have you automated? When do you do automation in your sprint? How many test cases have you automated per day?

Answer 6

Mostly I have automated functional regression tests (including smoke and regression, database, and API testing) and we do in-sprint automation for user stories. How about you how do you do automation in your company? When devs are done with their part, When code is deployed to QA/test environment. When testing framework is set up,When all manual tests are done When Smoke tests are passing It all depends on the functionali-ty and complexity of the scenario. I always follow coding standards and focus on the quality of my scripts no quantity. Sometimes just find a right locator and specify dynamic xpath takes time, Since I work in an Agile environment some days will be spent attending sprint meetings. When developers fix any bugs, I start on retesting that bug based on its priority and severity. and when some of the team members have any challenges and need my help, I always try to help them.

Question 7

Why does manual testing still exist, even though automation has been proven to be more efficient?

Answer 7

So, when adding a new feature, it’s important to start with manual testing to make sure it meets the acceptance criteria. Manual testing is cost-effective for simpler applications and provides flexibility. Yes, automation testing, is very useful, and involves writing test cases, but it can take longer for small changes. Manual testing adds a human touch to making sure user-friendliness, especially in identifying unexpected bugs and reproducing issues found by customers. In agile environments, manual testing adapts easily without extra work. While automation is good, manual testing stays critical for finding issues automation might miss.

Question 8

Let’s say you’re given some test cases; how do you decide them to automate or not? Can you tell me any specific factors?

Answer 8

Before I start automation, I do automation feasibility. There are multiple factors that I decide the test cases to automate such as Features that are critical to the application and if they fail cause important damage to the business, Tests that need to be run against every release of the application, such as smoke test and regression test, tests that are running more than once, tests that need to run against different OS & Browser combinations, tests that execute the same workflow but use different data for its inputs for each test run.

Question 8

Automation challenges and how did you solve them? What are the challenges you face when running automation scripts? Overall challenges?

Answer 8

I had a challenge overall on Selenium about switching frames a couple of times; in some applications for better visibility, developers use the frame concept in web pages, and in this case, if the element exists in frames, then we have to switch to that frame first by doing switchTo().frame() then once we are inside the frame, we can perform tasks on the elements within it using standard Selenium WebDriver commands (like find elements, send keys, click, etc.) once we are done with the frame we need to switch back To the parent window: and to do that, we use driv-er.switchTo.defaultContent();

Question 9

What challenges have you had in an agile environment?

Answer 9

Changing Requirements, Not Enough Information on the Story, Estimating Time for Completing Task, Waiting on Development to be completed before testing

Question 9

Tell us some key challenges you face in the Testing industry?

Answer 9

Requirements changing, when the application is not stable, rush testing to meet the deadline, Unclear requirements, Domain knowledge and business user perspective understanding, lack of Regression testing or not enough, lack of skilled testers, lack of resources, tools, and training.

Question 10

Tell me about your challenges?

Answer 10

As an Automation tester, I had several challenges during projects I have worked on. so sometimes it can be tough when requirements are not clear or keep changing. This can affect how we test things, it’s important to communicate well and make sure we’re testing what’s needed. Being clear about what we’re testing helps us find and fix problems early. This and other challenges (such as miscommunication, limited time, last-minute changes, etc.), I see these challenges as opportunities for my growth and improvement. Overcoming these difficulties requires a combination of technical knowledge, effective communication, and a hands-on approach to problem-solving. Continuous learning and adaptation are key to navigating the developing landscape of software development and QA. Technical: As a QA Engineer, I often deal with technical challenges when testing software. One big task is staying updated on different technologies and tools, so I make sure to learn continuously through training and exploring resources. This helps me adapt to changes and keep our automated tests effective for finding issues. Another challenge is making sure the software works well on various devices and browsers. Even though it’s tough, I focus on thorough testing and solving problems, contributing to delivering good-quality software that users like. Overall, my active learning and problem-solving approach help me handle technical challenges in my role as a QA Engineer.

Question 11

How did you conduct Batch Testing in your project? ( groups (batches)

Answer 11

When we run multiple scripts, with Automation Tool, that is called batch testing. We performing Batch Testing in Cucumber using the @Tags options for running the batch of test cases. But when I was using the TestNG Testing Framework I was using @groups.

Question 12

What drivers do you use in your framework?

Answer 12

I use ChromeDriver, InternetExplorerDriver and GeckoDriver. also according to our reports most of our users are using Chrome or Internet Explorer therefore we mostly perform our execution in the Chrome browser and ie. But we also try to utilize Firefox with Gecko driver in order to achieve compatibility within all browsers

Question 13

How would you handle test data in your framework? How do you run tests using excel data?

Answer 13

In my Cucumber framework, I use Scenario Outline, DataTable, and Excel with Apache POI for managing test data, while in my TestNG framework, I choose Excel with Apache POI and DataProvider for handling data effectively.

Question 13

Tell me about your reporting systems? Where do you store the test results/reports?

Answer 13

We are using Cucumber Reports, Reporting plays a very important role in any project because at the end of the day everyone is interested in seeing the reports, not the code. So, Cucumber provides a default HTML report and, in my project, we are using the Maven Cucumber plugin which is showing the percentage of passed and failed tests. It also offers a view with detailed execution status in numbers, it will also help the user to analyze and debug the issue. Users can also access the test data and Test evidence from reports, which are the most important aspects while fixing the bugs. And in the Testng reports, once we execute the tests, TestNG generates a test output folder at the project. It combines two kinds of reports. Detailed Report - report in the <index.html> file. It combines detailed information like the errors, test groups, execution time, step-by-step logs, and TestNG XML file. Summary Report - it is the trimmed version and informs about the no. of “Passed”/” Failed”/” Skipped” cases. You can see it from the <emailable-report.html> file. Extend Report - Extent Report is an HTML reporting library for Selenium WebDriver for Java. It is a great tool we can use within our automation framework to make excellent execution reports.</emailable-report.html></index.html>

Question 14

Walk me through the decision process of deciding which tests to automate;

Answer 14

I prioritize automating test cases that need to be run frequently, like regression, smoke, and sanity tests. Before deciding which ones to automate, I make sure the application is stable. I avoid automating tests for frequently changing features or those that run rarely or only once. I choose usability and exploratory testing for these scenarios.

Question 14

What are the advantages and disadvantages of automation testing?

Answer 14

The advantages of automation testing is needs less people, can be reused, covers more tests, it’s reliable, it’s runs tests at the same time, and it’s fast, for the disadvantages it takes more time to develop and maintain, there’s costs for tools, it requires skilled people, setup is complex and debugging test scripts can be challenging.

Question 15

Tell us about your experience with different testing methodolo-gies. How do you decide which one to use for a specific project?

Answer 15

I’ve worked with various testing methodologies, including black box testing, white box testing, regression testing, exploratory testing, and acceptance testing. My choice of methodology depends on the project’s needs, development approach, and available resources. For example, in Agile projects, I typically select exploratory testing to adapt to that growing application. If this is a project with several test cases, I prioritize automation testing to save time. Before choosing the methodology, I carefully analyze project requirements to identify crucial testing features. My decision is then based on what is best fit for the project.

Question 15

If I hire you and ask you to come and start automation, how would you do it?

Answer 15

I start by checking if automation is a good fit for the application. If it is, I use tools like Selenium. First, I manually explore the app, find tests to automate, and do a quick smoke test for the basics. Then, I set up an automation framework for organized scripting, making sure the scripts are simple, reusable, and well-explained. I do regular checks and fix any issues. Before jumping into automation, I make sure it makes sense for the app, considering tests, tools, team size, and budget. Planning involves choosing a framework, scheduling, and communicating with the team. When writing test scripts, I focus on reusability and clarity. During execution, I aim for good coverage, stability, and efficiency. If there are any app-related issues, I report them. I analyze results using reporting tools and share findings with the team or client. So, this process involves checking, scripting, testing, and reporting for effective automation.

Question 16

Describe what you might like and dislike about the work?

Answer 16

I really like working on challenging projects where I can use my skills. I also like being part of a team where we share ideas and work together. On the not-so-good side, when things are unclear, like not knowing what’s expected, it makes the job harder for me. Also, not getting recognized for my work is something I don’t like much.

Question 17

Conflict management: “Describe a conflict you’ve had with other staff members and how you resolved it

Answer 17

in my previous job, our team had a tough project with a tight deadline. There was a disagreement between the development and testing teams about fixing bugs. I organized a meeting to talk about the issues, encouraging open communication and teamwork. We decided to focus on the most important bugs and setting up a better way for the teams to communicate. This improved how well the teams worked together, kept the project on track, and met quality standards. Resolving the conflict made the team more efficient and contributed to the project’s success.

Question 17

Please tell me about a time when you saw room for improvement in some area of your work environment or a process that could be more efficient. What would be your action towards it?

Answer 17

Once, I noticed that the bug reporting process was causing delays in fixing issues. The current system was unclear, causing misunderstandings between the development and testing teams and slowing down the project. Seeing the need for improvement, my task was to make the bug-reporting process smoother for better communication and faster issue resolution. To address this, I started by reviewing the current bug-reporting workflow. I worked with the team to understand their challenges, and we found that there were inconsistencies in the information provided, making it hard for developers to understand and fix reported issues. In response, I suggested using a standardized bug-reporting template. This template included important details like steps to reproduce, expected and actual results, and system configurations. I also encouraged the use of screenshots and screen recordings to give a clearer picture of each reported bug. To make sure everyone could use the new template effectively, I managed training sessions for the team. I also set up regular feedback sessions to make any necessary improvements. The introduction of the standardized bug reporting template significantly improved the efficiency of the bug resolution process. Clear bug reports led to faster issue fixing by the development team, and communication between the teams got better, reducing the time spent on clarifications. As a result, we kept better track of project timelines, and the quality of the software we delivered improved. This experience confirmed my ability to identify problems, suggest practical solutions, and make changes that positively affected the team’s efficiency and project outcomes.

Question 18

Describe a time when your supervisor or a co-worker asked you to help out and doing so required extra work outside your established responsibilities or staying later than you anticipated. What did you do, and how did you feel?

Answer 18

So, one time when my co-worker immediately needed assistance with our project. Although it fell outside my regular responsibilities, I knew the importance of the task and I happily accepted to help. This involved putting in extra hours and working beyond my usual schedule to meet the project deadline. I quickly reviewed the requirements, prioritized my tasks, and reorganized my schedule to adapt to the additional workload. While it required personal sacrifices and extra effort, I understood the importance of supporting the team and ensuring the project’s success. Throughout the process, I maintained open communication with my supervisor and kept them informed about the task and the steps I was taking to manage the workload. Despite the initial challenges and added pressure, the successful completion of the project brought a sense of accomplishment and strengthened the value of teamwork and flexibility in achieving common goals.

Question 18

Describe an occasion when you had two bosses ask you to do conflicting tasks. How did you handle this dilemma?

Answer 18

Sure Once, I faced a dilemma with conflicting tasks from different supervisors. One wanted a critical bug fixed immediately that appeared in the production environment, while the other prioritized a long-term testing plan. To fix this conflict, I had a brief meeting with both supervisors, openly discussing the conflict and suggesting a solution. I suggested focusing on fixing the critical bug first, with clear communication about a potential delay in the testing plan. This way, we ensured stability in the production environment and committed to giving full attention to the testing plan once the critical issue was resolved. Both supervisors agreed to this approach. Implementing the plan, I quickly resolved the critical bug, preventing any production environment issues. Although the testing plan experienced a delay, it received focused attention after resolving our critical bug. Open communication with both supervisors led to understanding and cooperation, maintaining a positive working relationship. This experience demonstrated my ability to manage conflicting priorities, communicate effectively, and find a balanced solution that addresses both immediate and long-term goals.

Question 19

Tell me about a time when your job required you to perform a task that you didn’t know how to do. How did you respond?

Answer 19

Sure, so during a project, there was a time I switched to a new team in the company, so I faced a new feature that I needed to test, but I didn't have enough information about it. However, I immediately took action to understand the feature and get the necessary information to test it effectively. First, I communicated with my development team to understand how the feature worked and its expected behaviors. Next, I referred to documentation and available resources to learn about the feature, the documentation was also unclear so I reached out to other QA engineers to understand how similar features were tested and communicated with them to understand the overall structure of the project. Additionally, I collaborated with developers to gain more insights into the feature and focused on creating test scenarios. As a result, I initially took steps to bridge my knowledge gap, and then, using the learned information, I developed an effective testing strategy. This experience enhanced my ability to learn quickly and actively solve these kinds of problems.

Question 19

How do you feel about working in a team environment working

Answer 19

I really like collaborating with different people because it helps us come up with better solutions. I enjoy using my skills and learning from others. Talking openly is crucial, and I always try to communicate openly with my team. Teamwork not only helps us solve problems but also makes work positive and enjoyable. I especially like the feeling of success when we achieve our goals together.

Question 20

What is your greatest strength and how will it help your performance in this position? / What are some of your strengths? / What are your greatest strengths and accomplishments?

Answer 20

My greatest strength is adaptability, which allows me to effectively navigate complex situations. In the dynamic role I am applying for, where requirements can change, and unexpected challenges may arise, my adaptability ensures quick adjustment to new circumstances. I am skilled at staying positive in challenging situations, working collaboratively with others, and effectively communicating my ideas. Additionally, I have a strong feeling for learning new things and adapting to changes easily. My key strengths include organizational skills, effective communication, and practical problem-solving. I have successfully managed testing projects, improved efficiency through automation, and a positive team environment.

Question 21

How do you handle stress and pressure?

Answer 21

I manage stress and pressure by breaking tasks into smaller parts, setting realistic goals, and taking breaks when needed. Seeking help is crucial in overcoming challenges. Additionally, I use stress as a motivational tool by focusing on set deadlines. I successfully applied these strategies, for instance, when intensely focusing on a project's deadline. This approach made the project more manageable, minimized stress, and supported a successful delivery. Overall, adopting a balanced strategy facilitates my ability to cope with stress in professional settings.

Question 22

Give me an example of a time you were able to be creative with your work. What was exciting or difficult about it?

Answer 22

As a QA engineer, I faced the challenge of testing a complex financial software update. To ensure thorough coverage for new features while maintaining efficiency, I introduced a risk-based testing approach. Collaborating closely with the development team, I prioritized high-risk areas and implemented exploratory testing sessions to uncover issues creatively. Automated scripts were designed for repetitive tasks, freeing up time for more exploratory testing. This strategy identified critical issues early, improved overall testing efficiency, and positively shifted the team's mindset towards a more flexible testing approach. This experience highlights my ability to think creatively, adapt methodologies, and navigate challenges in introducing innovative testing approaches.

Question 22

What do you expect from a supervisor? (Project Manager, Team Leader)

Answer 22

I expect my supervisor to give clear instructions and guidance. It's important that they support and help me when I need it. Regular feedback is also helpful so that I know how I'm doing, also after every sprint I ask how was my performance during that sprint. I appreciate a supervisor who communicates openly and listens to any concerns I may have. A good supervisor creates a positive work environment and helps the team succeed.

Question 22

Can you tell me about a time when things didn’t work out well?

Answer 22

There was a time when a critical software release didn't go well. I had to find the issues fast and make sure future releases went smoother. I analyzed the release process with the development team, finding miscommunication and last-minute changes as key problems. To fix this, I suggested a better testing plan and improved communication to reduce last-minute changes. These changes improved later releases, finding issues earlier and making the process smoother. This taught me the importance of proactive testing and good communication for successful software releases.

Question 23

Tell me about a time you were dissatisfied in your role. What could have been done to make it better? (Note: never mention anything bad or rude about your previous employer)

Answer 23

In my role, I faced communication challenges within the team. As solution, I started regular team meetings and try to keep positive active, and happy slack environment .This approach improved team satisfaction and transparency. Looking back, structured onboarding and communication tool training could have helped from the beginning.

Question 24

Have you ever failed to accomplish a task?

Answer 24

Yes, not failed, but once I had a complex automation task within the expected timeframe. My job was to make testing more efficient by automating complex scenarios. But I faced challenges. I talked to the team, asked for help, and took online courses to understand automation better. Changing my approach and breaking down the task worked. It was tough at first, but with teamwork and learning, I didn’t; failed, I succeeded. This taught me how important it is to adapt and keep learning in QA.

Question 25

Questions to ask the interviewer/ Do you have any questions?

Answer 25

1. Can you tell me more about the day-to-day responsibilities of this job? 2. What is the onboarding process like for new employees? 3. What are the company’s expectations from the employee during the first month, second month, and year?

Question 26

Why should we hire you?

Answer 26

I have the right skills for the job, a positive attitude, and I work well in teams. I learn quickly and can contribute right away. I left my previous projects on good terms and can bring that commitment here.

Question 27

Where do you see yourself in five years? / Where do you see yourself in the future?

Answer 27

I want to keep learning and become more technical. Learning multiple programming languages and new tools is important to me so that I can contribute to the organization. In the future, I see myself as a QA lead, using my skills to help the team.

Question 27

I see you're a Quality Assurance Engineer, but you have a degree in health. how come?

Answer 27

I studied health in university as per my family's wishes. However, during my first year, I found a strong interest in programming. Despite this change, I completed my health degree to fulfill my family's expectations. Now, as a Quality Assurance Engineer, I've gained skills in technology, showcasing my commitment to learning and adapting.

Question 28

What are some of your major weaknesses?

Answer 28

Sometimes, I can be overly critical of my own work, leading to occasional self-doubt. To address this, I actively seek feedback and continuously work on maintaining a balanced perspective. Additionally, I tend to invest more time in perfecting details; therefore, I am working on finding the right balance to ensure both care and efficiency in my tasks.

Question 29

Tell me about a time you had to work closely with someone whose personality or work style clashed with yours?

Answer 29

Yes, once I had to work closely with someone who had a different personality and work style. To handle it, I focused on doing my job well without expecting too much friendship. I kept things professional and polite when we interacted, knowing we were different. Rather than trying to be close, I became friends with other colleagues who worked more like me. By concentrating on our tasks and being respectful, I tried to make the work environment good for everyone.

Question 30

What do you do in your spare time outside of QA?

Answer 30

In my spare time outside of QA, I'm actively involving in volunteering. I work with various associations where I've initiated and managed projects. My responsibilities include organizing meetings, and providing mentorship, and, I've even taught coding to kids. Apart from these, I've been involved in numerous other projects as well.

Question 30

What’s been the toughest criticism you received so far in your career? What did you do with it?

Answer 30

Yes, once there was a period when I felt exhausted and worked hard to meet deadlines. During meetings, I didn't realize that I wasn't speaking up enough, and my team lead expressed her concern to me. Then, I understood that I lacked of motivation. To address this, later that week I changed my weekend off to my quick weekend holiday and went to refresh myself, and I returned to work with renewed energy and focus.

Question 31

Have you ever mentored or supported an employee? What was your approach?

Answer 31

Yes, in my current role, I mentored junior QA engineers during their onboarding process. I created a detailed plan with essential information, links, and project insights for them. Encouraging questions and conducting knowledge transfer meetings, I provided demos and assistance. The onboarding went well, and my manager appreciated the comprehensive document I prepared.

Question 32

What to do in case of you have too much work and you cannot finish by the deadline?

Answer 32

When developers delay code deployment, our testing team faces time limitations. To address this, I proposed increased collaboration and daily communication with developers during the Sprint Grooming Meeting. Some team members prioritize task completion over test coverage. I align my priorities with the test lead and manager for more effective work focus.

Question 32

If there isn’t enough time for testing, what would you do?

Answer 32

If we are short on time, I would prioritize my test cases and tackle ones that cover most functionalities and I will also check with my team members if they can help out since I have been on agile projects where we work together in such matters. So when we prioritize we look for; Which functionality is most visible to the user?, Which functionality has the largest safety impact?, Which aspects of the application are most important to the customer?, Which aspects of the application can be tested early in the development cycle?, Which parts of the code are most complex and thus most subject to errors?, Which parts of the application were developed in rush or panic mode?, Which parts of the requirements and design are unclear or poorly thought out?, What do the developers think are the highest-risk aspects of the application?, What kinds of problems would cause the most customer service complaints?, What kinds of tests could easily cover multiple functionalities?

Question 33

How many people are on your team or describe me to your team? / Tell me about your current Scrum Team, what is your role, how many people are there? Can you talk about your team structure?

Answer 33

Our team consists of 3 developers, 1 dev lead, 1 product manager, 1 scrum master, 1 UX designer, and 2 QA testers including me. Our roles and responsibilities as testers are maintaining the framework by implementing smoke and regression suites. Collaborating and communicating with each other effectively to contribute Agile-Scrum environment.

Question 33

Describe scrum? Scrum Framework

Answer 33

In Scrum, there are three main roles: the Scrum Team, which includes 5-9 members like Developers, Testers, and Business Analysts; the Product Owner, responsible for explaining the project idea and managing the product backlog; and the Scrum Master, who guides the team and addresses any issues. Scrum ceremonies are important events in the process. They include Sprint Grooming, where we refine user stories; Sprint Planning, where we select and estimate effort for backlog items; Sprint Demo, where we show developments to stakeholders; Sprint Retrospective, where we learn from past sprints; and Daily Scrum, a quick daily meeting. Scrum artifacts are key documents. The Product Backlog represents the entire application; the Sprint Backlog contains items for a specific sprint, and the Burndown Chart shows the progress during the sprint.

Question 34

What are the three roles of an Agile team?

Answer 34

Product Owner, responsible for explaining the project idea and managing the product backlog; and the Scrum Master, who guides the team and addresses any issues. Scrum ceremonies are important events in the process. The Team Member which includes 5-9 members like Developers, Testers, and Business Analysts

Question 34

Tell me about your agile process:

Answer 34

: Absolutely so in my current role, we use Agile a lot. This means we focused on being flexible and working together. Our work was split into 2-week parts called sprints. In each sprint, we had important meetings like Sprint Planning, Mid-Sprint, Sprint Demo, and Sprint Retrospective. Besides those, we also had extra meetings. After every sprint, we had grooming and knowledge transfer sessions. These helped us understand how the project was going and learn from each other. Before each sprint, we planned things in Sprint Planning. We also had Sprint Grooming to talk about the details of the work. Then every day, we had a quick meeting called a standup. We talked about what we did yesterday, what we're doing today, and if there were any problems. At the end of each sprint, we showed what we did in a Sprint Demo. As a QA person, I often explained technical parts. Then, we had a Sprint Retrospective to talk about what went well and what could be better next time. We also planned a release after every sprint. This means we shared our work regularly, which is an important part of Agile. So, my experience in Agile processes has given me a good understanding of how to work well in a team and improve our work in each round. In addition to these regular activities, we also focused on continuous learning, regularly checking in with each other, and adapting our plans based on feedback to make sure our project's success.

Question 35

Tell me about your role and responsibilities? / Role - (Tell me about your role)

Answer 35

My role as an automation engineer is to analyze and automate test cases to efficiently find defects to improve the quality of the product and maintain, and automate my regression suite, in a continuous integration environment, my team and I handling weekly regression tests and also a major regression test before every release. I am also in charge of running daily smoke tests and analyzing these results actively participating in Agile ceremonies. If issues for service problems, I promptly contact developers, if script-related, I debug my scripts, for identified bugs, I reproduce and log defects. I use JIRA as a bug-tracking tool. Once developers fix reported bugs, I retest, and if the fix is successful, I close the bug. If not, I reopen it. Also, in addition to my responsibilities of automating the web application in test, I am also I charge of performing Database testing using SQL and for the API I use postman. Lastly, I am a cross- functional team member that is always willing to help my team in any way to achieve our sprint goal(s).

Question 36

Why are you looking for a change now? / Why are you looking for a JOB?

Answer 36

I'm looking for a new job because my current project is ending soon although I have been extended an offer, I believe it’s the right time to look for new opportunities even though I've enjoyed my current role very much. I'm seeking a change for new challenges and professional growth if the right opportunity comes, I will take it.

Question 37

Can you start tomorrow?

Answer 37

Unfortunately, I can't start tomorrow because it wouldn't be fair to my current company, and my team wouldn't be happy. It doesn't seem professional, and I've never done that before. I'm sorry, but I need to share my automation framework knowledge with my team before I leave.

Question 37

What compensation are you looking for?

Answer 37

With my experience and expertise in this field, I am seeking a salary between $X and $ Y for my next role. I have researched comparable positions and spoken with individuals in similar organizations to confirm this range. I am confident that I would bring value to your team and am eager to learn more about the role's budget and other employee benefits. (“What are you offering for this position?” or “What do you usually pay for a QA position at this level?” “What is the range that you have for this position?” It’s always better to hear a number from them first!)

Question 38

How soon can you start a new job?

Answer 38

After I get an official offer letter, I need to give 2 weeks’ notice to my current employer. Would that be fine for you?

Question 39

Can you provide us with references and may we contact them?

Answer 39

Yes, I can provide you references after I get submitted and have an interview. I don’t want my colleagues to be bothered unless I have something firm. Also, I do get calls regularly since I am in the market, and I don’t want to be giving references unless certainly getting interviews.

Question 40

Can you provide your corporate email or for your references provide corporate email?

Answer 40

Unfortunately, I'm not able to provide a corporate email as it goes against company policy to use work email for personal matters. Instead, I can provide phone numbers for my references. Please let me know if there's anything else I can assist you with.

Question 41

Why do you have several different companies on your resume?

Answer 41

I have been a contractor for all my previous experiences and just like my current situation, and now I am looking for another opportunity!

Question 42

Why did you apply for this position or interested in this position?

Answer 42

I applied for this job because my current tasks are similar to those described in the job listing. I believe I can easily adapt to your company's requirements. I also like your company's values and think it's a good fit for me.

Question 43

What is the difference between a Client, Vendor and Subcontract-ing Company?

Question 44

Are you currently working as a full-time or contractor?

Answer 44

I have been working as a contractor, and my employment has been documented through 1099 forms.

Question 45

Who is your contractor company? “My contractor company is…………….

Question 46

Are you comfortable with Hybrid/In-office positions?

Answer 46

Yes, absolutely! I am very comfortable with hybrid or in-office positions.

Question 47

Are you willing to relocate?

Answer 47

Yes, I am open to relocation and excited about exploring opportunities that support my career goals

Question 48

Tell me you D2D activity/roles and responsibilities as a testing engineer

Answer 48

As a QA engineer, I usually start my workday at around 9:00 am. One of my initial tasks is to check emails and review smoke test results to making sure the stability of our application. If any issues appear, I promptly address them during our daily stand-up meeting, and maintain transparent communication within the team. After the stand-up, I interact with the Jira board, either selecting a new user story or continuing work on an existing one. Throughout the day, I actively participate in various meetings, collaborating with team members to stay informed. Whether creating test cases, executing them, or improving our automation framework, my goal is to maintain the highest testing standards and contribute to the overall success of our projects.

Question 49

The sprint is ending very soon, and you need to do a release, but you found a minor issue, what would you do?

Answer 49

If a small issue comes up right before the end of a sprint and we need to do a release, I carefully check how much it might affect the project. Then, I discuss the issue with the team to decide its priority. If the issue is not a big problem and won't impact critical functions, we may still go ahead with the release as planned. But, I make sure to write down all the details of the issue and plan to fix it more systematically in the next phases of our work.

Question 50

How often is your release?

Answer 50

We do the release after each sprint so every two weeks I can say. It happens mostly on Friday after 8 pm.

Question 51

Do you only do your testing, or do you help with developers and/or PO/BA with their job?

Answer 51

I am reliable when it comes to helping peers. On my current project we participate on different types of meetings. My BA once asked me to review some of the user stories with him because I can provide my feedback on testing side. I helped him write test cases and learn the functionality.

Question 51

You have 2 user stories with same/high priority, how would you make sure to finish both in a timely manner?

Answer 51

I always organize myself and work one task at a time. I have seen people work on both tests and that is dangerous because their mind is focused on not one story but two. So instead of making my life harder I know I can accomplish my deadlines if I plan accordingly.

Question 52

In a long-term project, many times the requirements change. Do the test plans also change along with the requirements? Please give detailed explanation

Answer 52

If you are working in an agile environment where requirements change frequently, it can be difficult to update the test plan every time a new requirement or change requirement comes in. The test plan is useful when we begin the testing process but as we proceed with it, we make fewer references to test plans. Practically, we are more focused on delivering the results than keeping the documentation updated. This might make a test plan inconsistent and outdated for further reference. Change management in test plan can be challenging for dynamic projects. But we can do as following: Design some flexibility into test cases; this is not easily done; the best bet is to minimize the detail in the test cases or set up only higher-level generic-type test plans. Focus less on detailed test plans and test cases and more on ad-hoc testing with an understanding of the added risk this entails. Focus more on initial automated testing on application aspects that are most likely to remain unchanged. Devote appropriate effort to risk analysis of changes, in order to minimize regression testing needs.

Question 53

Tell me about your ceremonies?

Answer 53

My team is an Agile team, we are following Scrum methodolo-gy, we do Daily stand-up meetings (Daily Scrum) everyday morning around 10:00 am, we have grooming meetings, Planning meetings, sprint retrospective meetings and sprint review meetings (Demo).

Question 54

Have you done Sprint demo?

Answer 54

I have conducted our Sprint demo couple of times. We sometimes have developers, Product Owner and testers do it. When I demo, I try to highlight what we’ve done as a team, what features we developed and tested, etc. I go over the UI or API endpoints that we’ve worked on.

Question 55

If the scrum master is not available, would you still conduct the daily stand-up meeting?

Answer 55

Yes, we can very well go ahead and do our daily stand-up meeting. I believe self-organized and well-communicated team members make the team stronger.

Question 56

What do you know about impediments in Scrum? Give some examples of impediments.

Answer 56

Impediments are the obstacles or issues faced by scrum teams which slow down their speed of work. If something is trying to block the scrum team from their getting work “Done” then it is an impediment. Impediments can come in any form. Some of the impediments are resource missing or sick team members, Technical, operational, or organizational problems, Lack of management supportive system, Business problems , and External issues such as weather, war, etc and lack of skill or knowledge

Question 57

Do you participate in your sprint planning meeting? When is your sprint planning meeting?

Answer 57

As a tester, I'm participating in sprint planning meetings and prioritize user stories. In our team, the sprint planning will be going on in the middle of the current sprint, but we discuss about for the next sprint user stories.

Question 58

What do you discuss on the Sprint Planning Meeting?

Answer 58

Usually, the product owner brings the user stories. The scrum team discusses about, user story negotiation, talk about acceptance criteria = requirements, make sure user stories are ready - definition of ready, Pointing: 1, 2, 3, 5, 8 grading what to done ---> according to complexity, and according to pointing you decide how long it will take time to complete during the sprint.

Question 59

What is a product increment?

Answer 59

An increment is the total of all the product backlog items completed during a sprint. This is eventually a small part of the "final" product. Each Product Increment should be potentially usable and available in the following as it is a step to reach our goal.

Question 59

What does Test case consist of?

Answer 59

A test case consists of pre-requisite or pre-condition details, test steps, test results indicating pass/fail, automation status, and the date of execution.

Question 60

How many environments do you have in your project?

Answer 60

Our project involves four environments: the Development Environment for unit testing, which is less stable than the testing environment; the Testing Environment where manual and automated tests repeat the production environment with periodic changes; the Pre-production Environment, acting as the User Acceptance Testing (UAT) area, with demos, load/performance testing, and automated regression tests before releases; and finally, the Production Environment, dedicated to post-release testing for software stability.

Question 61

Do you participate your grooming meeting? what is a grooming meeting? when do you have grooming meetings?

Answer 61

Yes, I have participated in grooming meetings as a part of the QA team. In the Sprint Grooming meeting, we discuss user stories more in depth with the development team and ask questions about stories. We do Sprint Grooming meeting one week before the sprint planning meeting. It helps us to have more efficient sprint planning meeting.

Question 62

Tell me about the differences between Test case, Test script, Test scenario? who's responsibility to write test case and who's responsibility to write Test script?

Answer 62

The test case is a documentation which describes step by-step how to perform testing. It includes test case ID, Precondition, step description, test data, expected result actual result, and pass/fail. The test scenario is a description of the user’s multiple actions that might face when using the applications. Test Scenario means " What to be tested" and test case means " How to be tested”. The test script in software testing is a set of instructions that will be performed on the system under test to test that the system functions as expected. This terminology is mostly used for automation testing.

Question 63

How do you test the application if the requirement is not available or not clear? What would you do if you end up with unclear requirements or requirements are not available?

Answer 63

In this case, I would start by testing things randomly to figure out what's needed. I'll check our meeting notes, emails, and discussions. Looking at any design sketches can also help. If I still have questions I start by talking to the Product Owner to reach out to the client or end-user, or I search for similar applications to gather information. After that, I discuss the issue with the developer, especially when working on production defect tickets without clear requirements. For my final step I would share my findings and and testing approach with the team in our daily meeting, and we make decisions together.

Question 64

What would you do if you end up with unclear requirements or requirements are not available?.

Answer 64

My experience and common sense are important, and I'll try to see things from the customer's perspective. If I have questions, I'd ask the Business Analyst or Product Owner for clarification.

Question 65

How do you get test data?

Answer 65

There are several methods to get the test data, such as typing it in manually, using database queries with SQL, using tools like Faker to generate data, making API calls for external connections, masking sensitive data, copying a part of production data, working with the development team for specific datasets, and combining these methods based on testing needs and diversity requirements.

Question 66

Is it possible to develop 100% bug-free applications? Why?

Answer 66

Making applications completely free of bugs is really hard because software is complicated, it runs in different places, people can make mistakes, requirements might change, and there could be problems we don't know about. Also, it takes a lot of time and resources. Even though it's tough, in software development, we try our best to reduce bugs through testing and teamwork to create good-quality software that works well for users.

Question 67

Can you do 100% manual testing and find all bugs?

Answer 67

It's not possible to cover every scenario, but testing all functionalities helps reduce the risk of bugs, ensuring a quality product that satisfies end-users and the client.

Question 68

Why do we need to test?

Answer 68

Testing is important in software development to identify and fix defects, assure quality, address risks, providing a good user experience, following standards, achieve cost savings, continuous improvement, and satisfy the customers.

Question 69

Can you tell the difference between STLC (Software Testing Life Cycle) and SDLC (Software Development Life Cycle)?

Answer 69

Sure, so in SDLC: During the Requirements Gathering/Analysis Phase, stakeholders collaborate to define project expectations and gather crucial information, followed by the Design Phase where the software product is designed with plans drawn up and continuous client meetings for approvals, and then the Coding/Development/Implementation Phase sees the implementation of the design through program writing, either individually or collaboratively. Testing in this SDLC phase includes a comprehensive process through the Software Testing Life Cycle (STLC) stages: Requirement Analysis, Test Planning, Test Case Development, Test Environment Setup, Test Execution, and Test Closure; finally, the Production Phase/Deployment and Maintenance stage deploys the code into the production environment and ensures ongoing functionality and improvement. In the Requirement Analysis phase of STLC, the quality assurance team ensures a clear understanding of project requirements, consulting stakeholders if needed, followed by Test Planning where effort and costs are estimated, and resources, test environment, limitations, and schedules are determined; during Test Case Development, the testing team documents detailed test cases and prepares required test data, while Test Environment Setup, an independent activity in STLC, ensures readiness for testing; Test Execution involves executing test scripts, performing maintenance, and reporting bugs, and Test Closure marks the final stage, completing tests and reporting results.

Question 70

Why do Software Applications have bugs?

Answer 70

There are various reasons why a system might have bugs, such as bad design, coding errors, miscommunication, continuous changes in requirements, rushing to meet deadlines and also the complexity of the application.

Question 71

Can you tell the Difference between Verification and Validation?

Answer 71

Verification is like double-checking documents to make sure we're creating the right product without looking at the code. It involves reviewing requirements, designs, and test plans to cover all scenarios. Non-functional testing, such as performance testing, is a part of it. Validation is when we execute our test cases, actually writing code to check if the system works as intended. It's about testing the real functions of the application to ensure everything runs smoothly.

Question 72

What is the difference between static and dynamic testing?

Answer 72

Static Testing (Verification Stage) is like a pre-check for code. Developers use a checklist to find errors in their code without actually running the program. It involves activities like Code Reviews, Inspections, and Walkthroughs. Dynamic Testing (Validation Stage) is the real-deal testing. It happens during the validation stage by running the application with real inputs to see if it produces the expected output. Examples include Integration Testing, System Testing, Regression, and Acceptance Testing.

Question 73

What Is the Difference between Black Box and White Box testing?

Answer 73

Black Box Testing is like exploring the outside of a product. It relies on product requirements and specifications. It's basically testing the front end without needing to know how the software works internally. No knowledge of coding or internal structures is required. White Box Testing is when you have insider knowledge. You know the internal structure of the application, including the code, and can perform unit testing. It's like looking inside the box, checking how things work within the software.

Question 74

Can you tell different types of testing you have experience with?

Answer 74

So I have an experience with smoke, regression, ad-hoc – exploratory testing, retesting, , functional, Positive-Negative testing, API testing, and Database testing. I use these tests frequently.

Question 75

Can you tell different types of testing you are aware of?

Answer 75

Sure, so I am aware of Unit testing (but I don’t do it), Integration testing, Regression testing, Ad-Hoc, Smoke testing, Performance testing, System testing, and UAT Testing

Question 76

In which phase should testing begin?

Answer 76

Testing should start at the requirements phase. At the very beginning.

Question 77

What is Ad-Hoc Testing? Exploratory testing?

Answer 77

Ad-hoc testing involves informal and unplanned testing without predefined test cases. Testers explore the application randomly, conducting both positive and negative tests. Exploratory Testing is a dynamic approach where testers simultaneously design, execute, and learn during testing. It involves exploring the software and adapting the testing process based on discoveries.

Question 78

What is unit testing, and have you ever done unit testing?

Answer 78

No, I haven't done unit testing. Unit testing is performed by developers before deploying their code from the development environment to the QA environment.

Question 79

What is the difference between UAT and QA? What is Acceptance testing?

Answer 79

QA is one lower environment to UAT. In some teams QA can be a separate team that does functional testing and validation and after testing Passed the QA environment code is moved to the UAT (sometimes stage) environment. Where testing is conducted again to make sure no bugs have been missed. This is an extra level of testing. UAT could be conducted in many ways in different companies. Acceptance testing is another name for UAT. UAT can be performed by business-side SMEs in your company. UAT can be performed by another UAT tester team in your company. UAT can be performed by client-side UAT testers at clients' companies. UAT can be performed by third-party UAT testers that clients hired.

Question 80

What is Integration testing?

Answer 80

Integration testing is when we check if different parts of a system work well together. For example, a website like Amazon, it is ensuring that features like search, payment, and recommendations function smoothly as a unified system. This testing helps find and fix any issues that may arise when combining these parts, ensuring the entire system works correctly.

Question 81

What is system testing (End-to-end testing)?

Answer 81

This testing covers the entire system, including Front-end, Back-end, Database, Server, Hardware, and related Software. The aim is to simulate a real user scenario from start to finish. The goal is not only to validate the system but also to ensure that its sub-systems work and behave as expected.

Question 82

What is Beta Testing?

Answer 82

Beta testing collects feedback from real users after the product is installed, typically at the client's end. This approach is also observed in the gaming industry, where a game is released to a specific audience before a broader release to gather valuable feedback.

Question 83

What is 508 Compliance testing

Answer 83

Government websites must be 508 compliant, ensuring accessibility for people with disabilities, including specific fonts and features like text-to-speech. While I understand these requirements, I haven't directly worked on 508 compliances.

Question 84

What is Negative Testing and what is Positive Testing?

Answer 84

Negative testing is testing the application/system with a negative scenario using incorrect/invalid data and verifying if the application responds as expected. Positive testing is testing the application/system with correct and valid data and verifying if the application responds as expected.

Question 84

What is Boundary Testing?

Answer 84

Boundary testing checks if software accepts valid data within a specified range and rejects invalid data outside that range. For example, testing an input field from 0 to 100 ensures values stay between 0 and 100.

Question 85

What is non-functional testing? Have you done any performance testing?

Answer 85

No, I haven't performed Performance testing or Security testing. Performance testing was handled by a separate team.

Question 86

What is Functional testing?

Answer 86

Simply, testing any functionality is functional testing. Even as an Automation Tester, we are required to perform Manual testing before starting to write automation test scripts. However, in some companies, there are manual testers who are only responsible for creating manual test cases and executing them.

Question 87

What is a testing hierarchy?

Answer 87

Unit testing: Developers test their code to make sure the functionality they are working on is working. Component Testing is a standalone functionality that can work by itself. Integration Testing All modules are combined. When integrated, they still work together. System Testing all functional and non-functional testing. Hardware, Software, Database, and servers are also checked to ensure all the systems are working. Acceptance Testing (User Acceptance Testing) It's testing by the UAT team mostly the business/client-side team or hired UAT team that validates what the QA team tested before moving to production.

Question 88

What is the difference between regression testing and retesting?

Answer 88

Regression testing is performed if a new functionality is added or bug fix occurs and we want to make sure other parts of the application are still functioning correctly. Retesting is performed when a defect gets fixed and you have to retest the functionality to see if it is really fixed or not.

Question 89

What is a hotfix?

Answer 89

A hotfix is an emergency issue that needs to be fixed right away and does not need to go through a whole sprint cycle. It’s an exception where it can be developed, tested, and deployed in a few hours or a day since it’s an extreme priority and the client wants the critical issue fixed ASAP and deployed. These critical issues are also called ‘show-stoppers’.

Question 89

What is the difference between system testing and integration testing?

Answer 89

System testing is when the entire system is checked such as hardware, software, servers, databases, etc., whereas for integration testing, the integration between the individual modules is tested.

Question 90

When do you know if you have enough test cases for your project or a specific module

Answer 90

If each requirement has at least one test case, we can be sure everything is covered. The Requirements Traceability Matrix (RTM) is helpful as it maps requirements to test cases and test cases to bugs. This ensures that all functionalities are tested, and the system or module is thoroughly covered. The RTM acts as a valuable tool in tracking and confirming test coverage throughout the testing process.

Question 91

When is a test considered to be successful?

Answer 91

Tests that cover more functionalities and discover more errors in the software product are considered more successful. The whole purpose of a testing process is to discover as many bugs as possible and as early as possible cover as many scenarios as possible.

Question 92

What is a Test Plan?

Answer 92

The Test Plan document is usually prepared by the Test Lead or QA Manager and the focus of the document is to describe what to test, how to test, when to test, and who will do what test. Components of the Test Plans are Introduction, Test items, Features to be tested, Features not to be tested, Test techniques, Testing tasks, Features pass or fail criteria, Test environment (Entry criteria, Exit criteria), Test deliverables, Staff and training needs, Responsibilities and Schedule

Question 93

What is the Entry and Exit Criteria in STLC?

Answer 93

Entry Criteria are things needed before testing, and Exit Criteria are requirements before finishing testing. Both apply at all stages in the Software Testing Life Cycle (STLC). Ideally, you move to the next stage only when the exit criteria of the previous stage are met, but practical issues may affect this. This tutorial focuses on activities and things to produce in each STLC stage.

Question 94

What is a Test Strategy?

Answer 94

A Test Strategy, managed by the project manager, outlines how we approach testing and sets standards. It covers Scope, Objectives, Roles, Communication, Industry standards, Automation, Testing metrics, Risks, and Defect tracking.

Question 95

Who is responsible for writing test cases and test plans?

Answer 95

Testers create test cases for different scenarios, and the test lead or QA manager is in charge of developing a test plan and reviewing our test cases.

Question 95

What is a test case and what does it include?

Answer 95

A test case is a document with steps to check a feature. It includes Test Scenario, Pre-Condition, Test Case ID, Test Data, Test Description, Expected Result, Actual Result, Pass/Fail, and Comments.

Question 96

What is the Requirement Traceability Matrix?

Answer 96

RTM links requirements to test cases and defects. It helps identify which specific requirement failed when a defect is found and ensures that no test cases are missing for a given requirement.

Question 97

What is test coverage?

Answer 97

We are testing the functionality of the application. Test coverage refers to the number of test cases we have and which functional areas they cover. It's crucial to determine if our test cases cover the entire application or if there are gaps in coverage.

Question 98

How do you define the bug life cycle?

Answer 98

The bug life cycle consists of different statuses that an error goes through. Examples include open, fixed, retest, reopened, reject, and closed.

Question 98

How do you deal with a bug which is not consistently reproducible?

Answer 98

The best approach is to take a screenshot of the bug. You can also capture a video if needed and make detailed notes. Discuss the bug with the team to ensure everyone is aware and can keep an eye on it.

Question 99

What do you do when you find a bug?

Answer 99

If I find a potential bug, I first retest it to confirm it's an issue. Then, I take a screenshot and log the bug in Jira with details like a short description, environment, steps to reproduce, severity, and priority so the developer can investigate.

Question 100

What would you do if a developer rejects your bug and refuses to fix it?

Answer 100

If a developer reject fixing a bug, I will retest it and check against the requirements. If the issue continues, I'd arrange a meeting with the BA and developers. In rare cases, if the problem still continues, I'd involve the QA or Project manager as a last option.

Question 101

Bug priority vs Bug severity?

Answer 101

so, bug priority is like our to-do list - it tells us how urgently we need to fix a bug, based on business needs. Bug severity, on the other hand, is all about the impact on the software itself - from big issues that stop everything (high severity) to small glitches that are more cosmetic (low severity). For instance, a bug that crashes the system is both top priority and high severity, while a tiny spelling mistake might be lower on our list - low priority and low severity. It's our way of figuring out what needs fixing first!

Question 102

What is the difference between bug release and bug leakage?

Answer 102

Bug release happens when a version of the software is launched with known bugs, typically of low severity/priority, as the company chooses to prioritize release over immediate bug fixing due to time or cost considerations. On the other hand, bug leakage happens when end users or customers discover bugs that were missed by the testing team during the software testing phase.

Question 103

Let's say you have a bug that comes in the day before the sprint is ending, do you let it go into production or move it to the next sprint?

Answer 103

Low-priority bugs are logged for future fixes and might allow production release, while showstopper bugs, presenting a risk of causing issues, prevent production release.

Question 104

How many bugs do you find a day?

Answer 104

We don't test every day due to meetings and the need to find time for creating and automating test cases. During actual testing, we initially find 2 to 3 bugs per day, which decreases over time to 0 to 1 bug as testing progresses.

Question 105

What is agile?

Answer 105

Agile is a way of developing software that highlights teamwork, delivering working software frequently, collaborating closely with customers, and adapting quickly to changes. Scrum is a specific approach within Agile that follows these principles.

Question 106

How is agile methodology different from than traditional waterfall process?

Answer 106

In Agile, software features are delivered regularly, allowing testing and development to happen at the same time. This shortens testing time since only small features are tested simultaneously. In the Waterfall model, testing occurs at the end of the entire development process, leading to a longer testing time as the entire product is tested in one go. Waterfall is a closed process with limited stakeholder involvement, while Agile involves various stakeholders, including customers.

Question 106

List some of the Agile Frameworks?

Answer 106

Scrum (70%), Kanban (5%), ScrumBan (8%), Extreme Programming (1%)

Question 107

When do we use Agile Scrum Methodology?

Answer 107

When the client is not so clear on requirements, when the client expects quick releases, when the client doesn’t give all the requirements at the same time

Question 107

What kind of projects are suitable for the Agile Scrum methodology?

Answer 107

The classic method works best for projects with clear requirements. But agile is good for projects with changing requirements where updates happen regularly.

Question 107

What is a parking lot?

Answer 107

This usually comes up in meetings, especially in daily stand-up but it's basically a problem not relevant to others in meetings and don’t want to discuss it to waste time there, this separate meeting can be arranged for it at a later time.

Question 108

Explain what Velocity stands for in Agile?

Answer 108

Velocity is the total story points a Scrum team finishes (meets the definition of done) in a sprint. It helps define the amount of work a team can complete in a sprint and estimates the time needed to finish a project.

Question 108

How do you track your progress in a sprint?

Answer 108

We track progress with a "Burn-Down chart." It's a visual representation showing the remaining work versus time.

Question 109

How often do you run your smoke and regression tests?

Answer 109

Even though this depends on the project I can say in my project; Smoke tests are run every day or with each new version to quickly check basic functionality. for regression tests automatically and regularly ensure that existing features continue smoothly after code changes, or if there I any new functionality added and also, we run the regression test before every release.

Question 110

What is Definition of Ready/ What is Definition of Done?

Answer 110

DoD stands for Definition of Done. It's met when: The story is development complete, QA is complete, Regression around the story is finished, and The feature is ready to be shipped/deployed in production.

Question 111

Is it possible that you come across different story points for development and testing efforts? In that case, how do you resolve this conflict?

Answer 111

It's common for the developer to assign a story point, like 3, while the tester gives it 5. We discuss and collaborate in the meeting to agree on a common story point.

Question 112

You are in the middle of a sprint and suddenly the product owner comes with a new requirement, what will you do?

Answer 112

Ideally, a requirement becomes a story in the backlog and is taken up in the next sprint based on priority. If it's high priority, the team can include it in the current sprint, but stakeholders need to be informed that it might result in some stories moving to the next sprint.