Task-1

1Q what are types of testing methods

1.static testing and dynamic testing: Static testing is testing, which checks the application without executing the code. It is a verification process. Some of the essential activities are done under static testing such as business requirement review, design review, code walkthroughs, and the test documentation review.

Dynamic testing :Dynamic testing is testing, which is done when the code is executed at the run time environment. It is a validation process where functional testing [unit, integration, and system testing] and non-functional testing [user acceptance testing] are performed

2.Black box Testing :In this method, tester selects a function and gives input value to examine its functionality, and checks whether the function is giving expected output or not. If the function produces correct output, then it is passed in testing, otherwise failed. The test team reports the result to the development team and then tests the next function. After completing testing of all functions if there are severe problems, then it is given back to the development team for correction.

3.white box Testing :white box testing which also known as glass box is testing, structural testing, clear box testing, open box testing and transparent box testing. It tests internal coding and infrastructure of a software focus on checking of predefined inputs against expected and desired outputs. It is based on inner workings of an application and revolves around internal structure testing. In this type of testing programming skills are required to design test cases. The primary goal of white box testing is to focus on the flow of inputs and outputs through the software and strengthening the security of the software.

4.Regression testing

5.Smoke testing, sanity testing

6.functional testing

7.Non functional testing : Load testing, stress testing, Volume testing, security Testing

2Q what are the different phases of STLC

the six phases of stlc :STLC consists of 6 phases where each has its entry-exit criteria and comes with associated activities and deliverables. Entry-exit criteria define when the phase starts and ends. Activities and deliverables define the actions taken within the phase and the results received. You can execute some of these phases together while others run more independently. These are the 6 phases of STLC:

Requirement Analysis

It is the first phase of STLC which deals with the QA team analyzing and understanding the requirement document to start the testing process with accurate information. in the Requirement analysis phase, the entry criteria are requirement documents, acceptance criteria, and understanding of the product architecture. The exit criteria for this phase are approved Requirements Traceability Matrix (RTM) and automation feasibility reports that evaluate if the tests can be automated. All of this ensures that the testing process starts with the right information and focuses on the important areas of the software.

Test Planning

After determining the user requirements, the next phase of STLC is to plan the tests. It is a critical step of STLC where all the test plans are defined, and a detailed strategy is laid out for the project. It includes developing test steps, assigning roles and responsibilities, and choosing the right testing approach and automation tools, if any. The QA team also calculates the estimated cost and resources to begin the testing. The entry criteria for the test planning phase are approved Requirements Traceability Matrix (RTM) and automation feasibility reports. The exit criteria are approved test plans, automation scripts, and defining the cost analysis of the complete project.

Test Case Development/Design

After finishing the planning stage, this phase is designing and developing the test cases. In this step, the testing team creates the test steps with proper input, test execution conditions, and expected output for execution. For the test case design and development phase, the entry criteria are approved test plans, automation scripts, and defining the cost analysis of the complete project. The exit criteria are the approved test cases and automation scripts with the proper information for each test step.

Test Environment Setup

This phase includes setting up a test environment to run your test cases and check the application for its efficiency. It decides the conditions to test your application and involves configuring and deploying the test environment. Often, this step also includes setting up test servers. You can either perform the test environment setup in sequence or execute it after the requirement analysis phase, as it is independent of all the previous phases. The entry criteria of this phase are requirement documents, system architecture details, and application design. The exit criteria are a fully up-and-running test environment to execute the approved test cases.

Test Execution

After all the setup and planning are over, the test execution phase comes. The QA team runs the test cases and scripts to check the quality of the application. They compare the expected results with the actual results to understand which areas have issues and need attention. The entry criteria of this step are the combined exit criteria of all the previous steps, including test plans/cases, test environment, user requirement document, and more. The exit criteria are all the executed test cases with results.

Test Closure :

The last phase of STLC is test closure which pertains to preparing a test result report. It summarizes the testing process and highlights the comparison between the actual and expected test results. The comparison includes the fulfilled project objectives, time taken to complete the testing, budget, test coverage, and identified issues. The entry criteria for the test closure phase are test results after executing all the test cases. The exit criteria are designed, delivered, and approved test results report.

3Q. As a manual tester, what are the qualities do you process ? provide examples to illustrate your points

1. Attention to Detail: A manual tester needs to have a keen eye for detail to identify even the smallest defects or deviations from expected behavior. Paying attention to every aspect of the software under test helps in thorough testing and ensures high-quality deliverables. For example, during UI testing, a tester with attention to detail would notice misaligned buttons, inconsistent font sizes, or incorrect color schemes that may affect the user experience.

2. Analytical and Critical Thinking: Manual testers should possess strong analytical and critical thinking skills to understand complex requirements, identify potential test scenarios, and assess the impact of defects on the software. They need to analyze the system’s behavior, think logically, and identify the root cause of issues. For instance, when encountering a functional defect, a tester with analytical skills would investigate the inputs, conditions, and expected outputs to pinpoint the underlying problem.

3. Communication Skills: Effective communication is crucial for a manual tester to convey information clearly and collaborate effectively with the development team, stakeholders, and other testers. They should be able to document their findings, write clear and concise defect reports, and articulate their testing approach. Additionally, good communication skills help in discussing requirements, clarifying doubts, and participating in meetings or discussions related to testing.

4. Persistence and Thoroughness: Manual testing often requires persistence and a thorough approach to ensure that all possible test scenarios are covered. Testers should be persistent in finding defects, executing test cases, and retesting resolved issues. They should be thorough in their testing efforts, leaving no stones unturned. For example, when performing regression testing, a persistent tester would thoroughly retest the entire affected functionality, even if the defect fix seems straightforward.

5. Adaptability and Learning Ability: Manual testers should be adaptable and open to learning. They need to work with different technologies, tools, and domains, and be willing to quickly grasp new concepts. They should stay updated with the latest testing techniques, industry trends, and emerging technologies. For instance, if a manual tester is assigned to test a mobile application after previously working on web applications, their adaptability will help them quickly understand the mobile-specific testing challenges and adapt their approach accordingly.

6. Time Management and Organization: Effective time management and organizational skills are essential for manual testers to handle multiple tasks, prioritize their work, and meet deadlines. They should be able to plan their testing activities, estimate effort accurately, and efficiently allocate time for different testing tasks. Being organized helps testers keep track of test cases, test data, and test environments. It enables them to work systematically and effectively manage their testing activities.

These qualities, along with domain knowledge, testing methodologies, and technical proficiency, contribute to a successful career as a manual tester. Developing and honing these qualities will enhance your effectiveness and value as a tester in the software development life cycle.

4Q.what are the differences between waterfall and agile methodologies in SDLC ?