Quality Assurance Wisdom Wave

 1. What are the phrases in SDLC?

  • Requirement analysis
  • Design
  • Development
  • Review
  • Testing
  • Integration

2. Why SDLC is important?

  • It provides a basis for project planning, scheduling and estimating
  • It provides a framework for a set of activities and deliverables
  • It is a mechanism for project tracking and control
  • It increases the visibility of project status to all the stakeholders
  • It helps to identify project risks beforehand

3. What are the QA responsibilities in each SDLC phrase?

Requirement analysis: Understand each requirement clearly and clarify when needed. Prepare traceability matrix for test case and requirement mapping

Design: Comes up with Test strategy, what to test and how to test

Development: Set up test environment and prepare test case documentation

Review: Understand what has changed what was done by the developer and what impact, check whether there is UT, IT coverage and decide what remains to automate.

Testing: Perform functional, and non-functional testing when needed

Integration: Perform regression tests and make sure the stability of the system. perform acceptance testing

4. What does it mean by testing shows the presence of defects?

We do the testing to identify the defects. But if we do not find any bugs doesn’t mean there are zero bugs.

5. Why early testing is important?

To identify defects in the early stages of SDLC

6. What does it mean by defect clustering?

Most of the issues are found around only a few modules. So executing the same tests again and again may not lead to finding bugs.

7.What does mean by pesticide paradox?

Repeating the same tests may not lead to finding new bugs. So test cases need to be regularly reviewed and revised and adding new test cases to find more defects needs to be done.

8. Is testing context-dependent?

Yes, testing a bank application may be different than testing a hospital system. So we need to change our approach, methodologies, and strategies based on the context.

9. What does mean by Absence of error fallacy?

fixing and finding bugs is not helpful if the system is unstable and does not fulfil the requirements.

10. What is the difference between verification and validation?

Validation: check whether we are building the correct system

Verification: Check whether the system we have built in is correctly working

11.What is a test plan?

It includes all the activities that need to be done to deliver a quality product.

  • Objectives
  • RoadMap
  • Introduction
  • Test items
  • Risk
  • Features to be tested
  • Features not tested
  • Approach
  • Items pass/fail criteria
  • Test deliverables
  • Environment needs
  • Resources
  • Schedules
  • Test results
  • Approvals

12. What is the fail-over test?

  1. validates a system’s capacity during a server failure to allocate sufficient resources toward recovery.
  2. When there are multiple servers that are up and running.
  3. Suddenly down the service of one server then make sure that the client connected to that server should be distributed among other servers

13. What is a resilience test?

Test the software to ensure that how it works under stress, under challenging situations

  • Down nodes in the load balancers.
  • Disable network interfaces.
  • Turn off application processes.
  • Unmount shared file systems.

14. How to do resilience testing?

1. Determine metrics.

Developers need to pick out which metrics should be monitored to show how well the software is performing. For example, metrics could be input and output times, throughput, time to recovery, and latency. Metrics could also include the relationship between metrics.

2. Identify baseline performance.

Now establish a baseline for the maximum load that the software can experience and still perform adequately. You need this base to help establish other variables seen in the testing.

15. Benefits and risks of test automation

Benefits

  • Time saved by reducing manual tasks
  • Execute regression test
  • Re-enter the same data set
  • Compare actual test results with expected results
  • Providing measures like test coverage
  • Reduce test execution time
  • Early defect detection
  • Early time to market
  • More time for testers to design new tests

Risks

  • High cost
  • Effort required to identify a tool
  • Maintain test scripting
  • Relying on the tool too much
  • Ignoring the human thinking
  • The dependency on the tool
  • The tool may go out of business
  • Vendor may sell them to another party
  • automation tool is not compatible with the development platform



Comments

Post a Comment

Popular posts from this blog

False Positive

 A false positive in software testing is when a test incorrectly indicates the presence of a defect or issue in the software when there actually is none. This means the test result shows a problem that doesn't exist, leading to unnecessary investigation and troubleshooting. Example: Imagine you have a test that checks if a login feature works correctly. The test is supposed to verify that users can log in with valid credentials. If the test fails and reports that the login feature is broken, but in reality, the login feature works perfectly fine, this is a false positive. Causes: Test Script Errors: The test script itself might have an error, causing it to fail even when the application works correctly. Environment Issues: Issues in the test environment, such as incorrect configurations or network problems, might lead to false positives. Timing Issues: Tests might run too quickly before the system has fully updated or responded, leading to incorrect failure reports. Impact: Wast...
Read more

100% Percent Test Coverage

  Testing Methodologies: Shift Left Testing: Focus on testing early in the development lifecycle, identifying and fixing bugs during development rather than later stages. This includes unit testing, code reviews, and static analysis tools. Agile Testing: Integrate testing closely with development in an iterative approach. As features are developed, tests are written and executed concurrently. Exploratory Testing: Encourage testers to explore the application freely, looking for unexpected behavior and usability issues. Model-Based Testing: Create models that represent the expected behavior of the system and use them to automate test case generation. Testing Techniques: Equivalence Partitioning: Divide the input space into valid and invalid partitions based on expected behavior. Create test cases for each partition. Boundary Value Analysis: Test cases around the edges or boundaries of valid input ranges (e.g., minimum, maximum values). Error Guessing: Based on your knowle...
Read more