Manual Testing Course -Day-20

 

Manual Testing Course Summary


  • Software Life Cycles & Processes - 
    • SDLC
    • STLC
    • Agile
    • Waterfall
  • Test Artifacts/Documents - 
    • Test Strategy
    • Test Plan
    • Test Estimation
    • Test Scenario
    • Test Cases
    • Requirements Traceability Matrix
    • Test Coverage
    • Test Data Management
    • Test Report
  • Testing Types - 
    • Manual Testing
    • Automation Testing
  • Testing Levels
    • Functional Testing - 
      • Unit Testing
      • Smoke Testing
      • Sanity Testing
      • Integration Testing
      • System Testing
      • Regression Testing
      • Acceptance Testing
      • Alpha Testing
      • Beta Testing
      • End to End Testing
    • Non-Functional Testing -
      • Performance Testing
      • Load Testing
      • Stress Testing
      • UI Testing (Graphical User Interface)
      • Usability Testing
      • Security Testing
      • Portability/Compatibility Testing
  • Testing Methods
    • Black Box Testing
    • White Box Testing
    • Gray Box Testing
  • Testing Techniques -
    • Boundary Value Analysis
    • Equivalence Partitioning
    • Decision Table
    • Use Case Testing
    • Error Guessing
    • State Transition
  • Test Management (tools) - 
    • Jira
    • Testlink
    • Github
  • Defect Management -
    • Bug Life Cycle
    • Bug Reporting
    • Defect Priority & Severity
    • Bugzilla (Bug Reporting tool)
  • Advanced Testing:
    • API Testing
  • Testing Keywords

Comments

Post a Comment

Popular posts from this blog

Manual Testing Course-Day 13

Image
  Manual Testing Manual testing  is a software  testing  process in which  test  cases are executed  manually  without using any automated tool. All  test  cases executed by the tester  manually  according to the end user's perspective. It ensures whether the application is working, as mentioned in the requirement document or not. What is Automation Testing? Automation testing is a Software testing technique to test and compare the actual outcome with the expected outcome. This can be achieved by writing test scripts or using any automation testing tool. Test automation is used to automate repetitive tasks and other testing tasks which are difficult to perform manually.  Performance Testing Performance Testing  is a software testing process used for testing the speed, response time, stability, reliability, scalability and resource usage of a software application under particular workload. The main purpose of performan...
Read more

Manual Testing Course-Day-18

Image
Manual Testing Interview Questions and Answers What does COTS represent? Commercial Off The Shelf. Commercial Off-the-Shelf ( COTS ) software is becoming an ever-increasing part of organizations' total IT strategy for building and delivering systems. A common perception held by many people is that since a vendor developed the software, much of the  testing  responsibility is carried by the software vendor. Why we split testing into distinct stages? We split testing into distinct stages because of the following reasons, Each test stage has a different purpose It is easier to manage to test in stages We can run different test into different environments Performance and quality of the testing is improved using phased testing 136. What is DRE? In order to measure test effectiveness, a powerful metric is used to measure test effectiveness known as DRE (Defect Removal Efficiency) From this metric we would know how many bugs we have found from the set of test cases. The formula for c...
Read more

Manual Testing Course-Day 8

Image
  What is a Test Scenario? A  TEST SCENARIO  is defined as any functionality that can be tested. It is also called  Test Condition  or  Test Possibility . As a tester, you should put yourself in the end user’s shoes and figure out the real-world scenarios and use cases of the Application Under Test. Scenario Testing Scenario Testing  in software testing is a method in which actual scenarios are used for testing the software application instead of test cases. The purpose of scenario testing is to test end to end scenarios for a specific complex problem of the software. Scenarios help in an easier way to test and evaluate end to end complicated problems. Why create Test Scenarios? Test Scenarios are created for the following reasons, Creating Test Scenarios ensures complete Test Coverage Test Scenarios can be approved by various stakeholders like Business Analyst, Developers, Customers to ensure the Application Under Test is thoroughly tested. It ensures...
Read more