DEV Community: Amrutha p m

Task 5:Test case and bug reporting

Amrutha p m — Mon, 25 Mar 2024 15:23:42 +0000

Q1)https://docs.google.com/spreadsheets/d/1gmvCM-jOvdAkFrPbK73pN6bt8_3XzK2OMkGnRPPr2Rc/edit#gid=0

Q2)Write the key points on — Test Scenario, Test Case, Test Strategy and Plan, Test Summary Report.

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, we should put yourself in the end user’s shoes and figure out the real-world scenarios and use cases of the Application Under Test.A test scenario is a description of a specific functionality or feature to be tested.Generally test scenario is written one line. It represents a specific condition or situation that needs to be verified during testing.
key points are,
1)It is to ensure the test coverage
2)Test Scenarios care approved by Business Analyst, Developers, Client to ensure the application Under Test is thoroughly tested. It ensures that the software is working for the most common use cases.It is to ensure the product's quality.
3)For studying and ensuring the end-to-end functioning of the program, Test Scenario is the most important one.
4)A test scenario doesn’t require such a detailed description as a test case does it is a one-line description is sufficient.
it saves time in overall stlc.
5)Test scenarios are usually written after brainstorming, so the chance of missing any behavior is minimal.
example: Check the login functionality

Test case:
Test cases are set of actions or functionality to be executed to verify particular features or functionality.which is under test scenarios.it included what we need to test and how to do the particular test case.To verifying a particular test case we need input sometimes and we need to follow certain steps to execute and to veryfy we need actual and expected results.Test cases which maps and traces the requirements.it helps to ensure the application is defect free.

Example
Test case id:TC_001
Test case :Verify that user can able to login with mobile number or not
verify that user can able to login with email id or not
verify that error message is displayed for invalid email id or not
verify that error message is displayed for wrong password or not
verify that user can login with valid email id and invalid password or not
verify that user can login with invalid email id and valid password or not
verify that user can login with invalid email id and invalid password or not
verify that user can login with empty fields or not
verify that user can login with valid email id and valid password or not

Test strategy:
A test strategy is a high-level document that defines the overall testing approach for a project.Test strategy provides a roadmap for how testing will be conducted. It ensures that testing efforts align with project goals and objectives.It provides a structured approach to the entire QA team, guiding them toward achieving testing objectives in the most efficient way.
key points
1)The test strategy document is approved and reviewed by the test team lead, development manager, quality analyst manager, and product manager.
2)The test strategy document specifies the resources, scope, plan, and methodology for different testing activities.
3)The test effort, test domain, test setups, and test tools used to verify and validate a set of functions are all outlined in a Test Strategy. It also includes schedules, resource allocations, and employee utilization information.
main components of test strategy document are,

Scope and Overview:Any product’s overview includes information about who should approve, review, and use the document.
Testing Methodology: Testing methodology is the next module in the test strategy document, and it is used to specify the degrees of testing, testing procedures, roles, and duties of all team members. The change management process, which includes the modification request submission, pattern to be utilized, and activity to manage the request, is also included in the testing strategy.
Testing Environment Specifications:The information about the number of environments and the needed configuration for each environment should be included in the test environment setup. For example, the functional test team might have one test environment and the UAT team might have another. Define the number of users supported in each environment, as well as each user’s access roles and software and hardwarerequirements, such as the operating system, RAM, free disc space, and the number of systems. It’s just as crucial to define the test data needs.
Testing Tools:Define the tools for test management and automation that will be utilized to execute the tests. Describe the test approach and tools needed for performance, load, and security testing. 5.Release Control: Release Control is a crucial component of the test strategy document. It’s used to make sure that test execution and release management strategies are established in a systematic way.
Risk Analysis: Risk Analysis is the next section of the test strategy paper. All potential hazards associated with the project are described in the test strategy document and can become an issue during test execution.
Review and Approval: When all of the testing activities are stated in the test strategy document, it is evaluated by the persons that are involved, such as, System Administration Team. Project Management Team. Development Team. Business Team. Starting the document with the right date, approver name, comment, and summary of the reviewed modifications should be followed. It should also be evaluated and updated on a regular basis as the testing procedure improves.

Test Plan:t’s developed from a set of software requirements(SRS).
A test plan is a comprehensive document that outlines the testing approach, scope, resources, schedule, and deliverables for a testing project.Test plan includes test objectives, test scope, test schedule, resource requirements, test environment, and exit criteria. It may also contain test deliverables, testing tasks, and responsibilities.
components and attributes of test plan are,

Objective: It describes the aim of the test plan, whatever the good process and procedure they are going to follow to give quality software to customers. The overall objective of the test is to find as many defects as possible and to make software bug-free. The test objective must be broken into components and sub-components. In every component following activities should be performed.Listing all the functionality and performance to be tested.Make goals and targets based on the application feature.
Scope: It consists of information that needs to be tested concerning an application. The scope can be divided into two parts: In-Scope: The modules that are to be tested rigorously. Out Scope: The modules that are not to be tested rigorously. Example: In an application A, B, C, and D features have to be developed, but the B feature has already been designed by other companies. So the development team will purchase B from that company and perform only integrated testing with A, B, and C.
Testing Methodology: The methods that are going to be used for testing depend on application to application. The testing methodology is decided based on the feature and application requirements. Since the testing terms are not standard, one should define what kind of testing will be used in the testing methodology. So that everyone can understand it.
Approach: The approach of testing different software is different. It deals with the flow of applications for future reference. It has two aspects: High-Level Scenarios: For testing critical features high-level scenarios are written. For Example, login to a website, and book from a website. The Flow Graph: It is used when one wants to make benefits such as converging and merging easy.
Assumption: In this phase, certain assumptions will be made. Example: The testing team will get proper support from the development team. The tester will get proper knowledge transfer from the development team. Proper resource allocation will be given by the company to the testing department.
Risk: All the risks that can happen if the assumption is broken. For Example, in the case of wrong budget estimation, the cost may overrun. Some reason that may lead to risk is: Test Manager has poor management skills. Hard to complete the project on time. Lack of cooperation.
Mitigation Plan: If any risk is involved then the company must have a backup plan, the purpose is to avoid errors. Some points to resolve/avoid risk: Test priority is to be set for each test activity. Managers should have leadership skills. Training course for the testers.
Roles and Responsibilities: All the responsibilities and role of every member of a particular testing team has to be recorded.

Example:
Test Manager: Manages the project, takes appropriate resources, and gives project direction.
Tester: Identify the testing technique, verify the test approach, and save project costs.

Schedule: Under this, it will record the start and end date of every testing-related activity. For Example, writing the test case date and ending the test case date.
Defect Tracking: It is an important process in software engineering as lots of issue arises when you develop a critical system for business. If there is any defect found ,defect tracking: Information Capture: In this, we take basic information to begin the process. Prioritize: The task is prioritized based on severity and importance. Communication: Communication between the identifier of the bug and the fixer of the bug. Environment: Test the application based on hardware and software. Example: The bug can be identified using bug-tracking tools such as Jira, Mantis, and Trac.
Test Environments: It is the environment that the testing team will use i.e. the list of hardware and software, while testing the application, the things that are said to be tested will be written under this section. The installation of software is also checked under this. Example: Software configuration on different operating systems, such as Windows, Linux, Mac Hardware Configuration depends on RAM, ROM, etc.
Entry and Exit Criteria: The set of conditions that should be met to start any new type of testing or to end any kind of testing. Entry Condition: Necessary resources must be ready. The application must be prepared. Test data should be ready. Exit Condition: There should not be any major bugs. Most test cases should be passed. When all test cases are executed.

Test summary report:A test summary report is a document that provides an overview of the testing activities, results, and overall quality of the software after testing is completed.
It provides the relevant stakeholders with a detailed account of the overall test results and defects.
It aims to summarize the results of the entire testing process formally.which includes,
A short evaluation of how well the testing is performed.
Quality of testing effort.
Quality assessment of the software.
The recordings should also include the factors like time taken, and different environments tested.
The incident reports included statistics.
A brief on the final test results.

Task 4: Agile Methodology

Amrutha p m — Mon, 18 Mar 2024 18:35:01 +0000

Q1)DIFFERENCES BETWEEN
VERIFICATION
1)Focuses on whether the software meets its specified requirements
2)Typically conducted during the development process
3)Involves testing at the component, module, and system levels
4)Involves testing with sample data
5)Designed to catch defects early in the development process
6)Examples include unit testing, integration testing, and system testing
7)Helps to ensure that the software is built correctly
8)Helps to increase confidence in the software
9)Improves the quality of the software
10)Can be automated or manual
11)Requires a good understanding of the software requirements and specifications

VALIDATION
1)Focuses on whether the software meets the needs of end-users
2)Typically conducted after the development process
3)Involves testing the software as a whole
4)Involves testing with real-world data
5)Designed to catch defects before release to end-users
6)Examples include user acceptance testing, alpha and beta testing, and compatibility testing
7)Helps to ensure that the correct software is built
8)Helps to increase user satisfaction
9)Reduces the risk of product recalls or legal issues
10)Often involves manual testing
11)Requires a good understanding of end-user needs and expectations

Example:
1)Verification of SUBMIT BUTTON in any Form or application
In verification aspect first we need to verify whether the submit button is available or not which in correct format correct place in correct manner or not.
Where as in validation process the application should have to perform some action whenever the user hits on the submit button.
Which would either save the data to the database or displays error message for the invalid data.
Verification starts even before we start the coding and continues throughout the development phase
Validation requires execution of the application after deployment.

SMOKE VS SANITY TESTING
SMOKE TESTING
1)Smoke Testing is performed to ascertain that the critical functionalities of the program is working fine
2)The objective of this testing is to verify the “stability” of the system in order to proceed with more rigorous testing
3)This testing is performed by the developers or testers
4)Smoke testing is usually documented or scripted
5)Smoke testing is a subset of Acceptance testing
6)Smoke testing exercises the entire system from end to end
7)Smoke testing is like General Health Check Up

Example:
1)verifying the user registration and login process
2)Checking the product catalog and shopping cart working as expected
3)verifying the products to add cart proceeded to checkout
4)Checking the payment service to complete the product purchase
5)Veryfing the product order confirmation and tracking order history

SANITY TESTING
1)Sanity Testing is done to check the new functionality/bugs have been fixed
2)The objective of the testing is to verify the “rationality” of the system in order to proceed with more rigorous testing
3)Sanity testing in software testing is usually performed by testers
4)Sanity testing is usually not documented and is unscripted
5)Sanity testing is a subset of Regression Testing
6)Sanity testing exercises only the particular component of the entire system
7)Sanity Testing is like specialized health check up

Example:
1)I want to add products to my shopping basket on an e-commerce website to make a purchase.
Scenario 1: Adding one item to the shopping cart.
Scenario 2: Adding numerous items to the shopping cart.
In Test Case 1, Confirm that a single item may be added to the shopping basket.
Verify that a user may add numerous products to the shopping basket in Test Case 2.

Q2)Explain about Agile methodology?
Automated Testing is a technique where the Tester writes scripts on their own and uses suitable Software or Automation Tool to test the software. It is an Automation Process of a Manual Process. It allows for executing repetitive tasks without the intervention of a Manual Tester.
It is used to automate the testing tasks that are difficult to perform manually.
Automation tests can be run at any time of the day as they use scripted sequences to examine the software.
Automation tests can also enter test data compare the expected result with the actual result and generate detailed test reports.
The goal of automation tests is to reduce the number of test cases to be executed manually but not to eliminate manual testing.
It is possible to record the test suit and replay it when required.
The different types of automation testing:
Unit testing: Unit testing is a phase in software testing to test the smallest piece of code known as a unit that can be logically isolated from the code. It is carried out during the development of the application.
Integration testing: component: Integration testing is a phase in software testing in which individual software components are combined and tested as a group. It is carried out to check the compatibility of the component with the specified functional requirements.
Smoke testing: Smoke testing is a type of software testing that determines whether the built software is stable or not. It is the preliminary check of the software before its release in the market.
Performance testing: Performance testing is a type of software testing that is carried out to determine how the system performs in terms of stability and responsiveness under a particular load.
Regression testing: Regression testing is a type of software testing that confirms that previously developed software still works fine after the change and that the change has not adversely affected existing features.
Security testing: Security testing is a type of software testing that uncovers the risks, and vulnerabilities in the security mechanism of the software application. It helps an organization to identify the loopholes in the security mechanism and take corrective measures to rectify the security gaps.
Acceptance testing: Acceptance testing is the last phase of software testing that is performed after the system testing. It helps to determine to what degree the application meets end users’ approval.
API testing: API testing is a type of software testing that validates the Application Programming Interface(API) and checks the functionality, security, and reliability of the programming interface.
UI Testing: UI testing is a type of software testing that helps testers ensure that all the fields, buttons, and other items on the screen function as desired.

Q3)Explain about EPIC and USERSTORIES?
EPIC ,the word meaning is greater in size.In Agile methodology epic represents a series of userstories that shares broader strategic objective.Epics are a helpful way to organize work and to create a hierarchy.The idea is to break the work into smaller pieces and the project gets done and regularly can update with the enduser or the client.An epic is a large body of work that can be broken down into a number of smaller stories or sometimes called “Issues” in Jira.
An epic is simply a collection of User stories,Which are interrelated to form a large application programme.
Benifits of epic are,Better time management and better organization and also clear cut priorities and customer statis faction.It brings transparency throughout the process.

USERSTORIES are lightweight tasks which covers the epic.During a sprint or iteration planning meeting, the team decides what stories they’ll tackle that sprint. Teams now discuss the requirements and functionality that each user story requires. This is an opportunity to get technical and creative in the team’s implementation of the story. Once agreed upon, these requirements are added to the story.Another common step in this meeting is to score the stories based on their complexity or time to completion. Teams use t-shirt sizes, the Fibonacci sequence, or planning poker to make proper estimations. A story should be sized to complete in one sprint, so as the team specs each story, they make sure to break up stories that will go over that completion horizon.

EXAMPLE:EPIC:Mobile app for an online beauty spa.
User story:1)Augumented reality so that the user a view virtually by applying beauty products.
2)Discounts and proomocodes
3)chat boat functionality for smaller queries.

Task 3 :STLC and QA Testing

Amrutha p m — Mon, 11 Mar 2024 04:29:48 +0000

Q1)List down all the models of SDLC?
SDLC stands for Software Development Lifecycle.Which is the end to end process included in complete development process.Each model follows a series of phases unique to its type to ensure success in the software development process.

SDLC MODELS ARE
1)Waterfall model
2)V Model
3)RAD MODEL
4)incremental model
5)Iterative model
6)BigBang model
7)Agile model

Q2)STLC — Software Testing Life Cycle,Also explain all stage of STLC
STLC stands for Software development Life cycle.The STLC is used to ensure that the software is of high quality, reliable, and meets the needs of the end-users.The stages of the STLC include Test Planning, Test Analysis, Test Design, Test Environment Setup, Test Execution, Test Closure, and Defect Retesting. Each of these stages includes specific activities and deliverables that help to ensure that the software is thoroughly tested and meets the requirements of the end users.
The main goal of the STLC is to identify and document any defects or issues in the software application as early as possible in the development process. This allows for issues to be addressed and resolved before the software is released to the public.

Phases:
1)Requirement analysis Phase Reviewing the SRS documentation and quality assurance team understands the requirements well like what is to be tested. If anything is missing or not understandable then the quality assurance team meets with the Development team/Bussiness Analyst/Tech Lead to better understand the detailed knowledge of the requirements. Identify the ambiguities, Identifying any missing or incomplete requirements, Identifying any missing or incomplete requirements,
2.Test Planning Identifies the objectives and scope of the test. Developing a test strategy like testing methods and techniques that will be used (agile method). Identifies the testing environment and resources needed. Identifies the test cases that will be executed.(RTM,Requirement tracebility matrix )and the test data that will be used. Estimating the time and cost required for testing. Identifies the test deliverables. Assigning the roles and responsibilities to the testing team, Reviewing and approving the test plan.
3.Test Case development Based on the requirement Tracebility matrix Test cases will be Mapped/prepared. The testing team also prepares the required test data/Scenarios for the testing. Test cases that are clear, concise, and easy to understand. Identifying the expected results for each test case. Reviewing and validating the test cases.
4.Test Environment Setup Once software test suites(Test cases) are designed, they need an interface to be executed in.This interface is called the Test Environment.It is created by integrating hardware,software,proper network configurations and data necessary to run tests. Mostly decided by the developer end or as per client requirement.
5.Test Execution In this phase testing team starts executing test cases based on prepared test cases. Once defect Logged in and FIxed by the developer Retest the same with test data and repot the result.
6.Test Closure Test closure stage is to ensure that all testing related activities have been completed and that the software is ready for release.And also it is to ensure that all relevent information related to testing that have been shared for future reference and enhancement.
example:NFT LAYER Requores and client says cant give this layer.then thematrix willnot be correct.

Q3)AS a test lead for a web –based application, your manager has asked you to identify and explain the different risk factors that should be included in the test plan. Can you provide a list of the potential risks and their explanations that you would include in the test plan?
Answer:

Product risk is the set of things that could go wrong with the service, software or whatever is being produced by the project.Risk is a combination of the probability and consequences of unfavorable events. This definition is also relevant for software projects but with more focus on their specifics.The software testing risks are:

1)incorrect scheduling (wrong project assessment, ineffective distribution of tasks, etc.)
2)constantly increasing or changing customer requirements (requirements change during the work on the project)
3)the failure of specifications (an overload of requirements or no exact requirements)
4)the loss of personnel (important technical staff members leave, and there isn’t enough time to replace them);
5)low productivity (the specialists are inexperienced, unmotivated, etc.).
6)Tight time limit that influence the testing flow.

Q4)4. Your TL (Team Lead) has asked you to explain the difference between quality assurance (QA) and Quality Control (QC) responsibilities. While QC activities aim to identify defects in actual products, your TL is interested in processes that can prevent defects.
How would you explain the distinction between QA and QC responsibilities to your boss?
QA
1)It focuses on providing assurance that the quality requested will be achieved.
2)It is the technique of managing quality.
3)It is involved during the development phase.
4)It does not include the execution of the program.
5)It is a managerial tool.
6)It is process oriented
7)The aim of quality assurance is to prevent defects.
8)It is performed before Quality Control.
9)QA is a low-level activity that identifies an error and mistakes that QC cannot
10)Pays main focus is on the intermediate process.
11)All team members of the project are involved.
12)It aims to prevent defects in the system.
13)It is a less time-consuming activity.
14)Verification

QC
1)It focuses on fulfilling the quality requested.
2)It is the technique to verify quality.
3)It is not included during the development phase.
4)It always includes the execution of the program.
5)It is a corrective tool.
6)It is product oriented.
7)The aim of quality control is to identify and improve the defects.
8)It is performed after the Quality Assurance activity is done.
9)It is a corrective technique.
10)It is a reactive measure.
11)It is responsible for the software testing life cycle.
12)It is a high-level activity that identifies an error that QA cannot.
13)Its primary focus is on final products.
14)Validation

Q5)Differences between manual and automation testing?
Manual Testing
1)In manual testing, the test cases are executed by the human tester.
2)Manual testing is time-consuming.
3)Manual testing takes up human resources.
4)Exploratory testing is possible in manual testing.
5)Manual testing doesn’t use frameworks.
6)Manual testing is not reliable due to the possibility of manual errors
7)In manual testing, the test results are recorded in an excel sheet so they are not readily available.
8)Manual testing allows human observation, thus it is useful in developing user-friendly systems.
9)Performance testing is not possible with manual testing.
10)In manual testing, batch testing is not possible.
Automation Testing
11)There is no need for programming knowledge in manual testing.
12)Manual testing is usable for Exploratory testing, Usability testing, and Adhoc testing.

Automation Testing
1)Manual Testing is possible without programming knowledge whereas Automation Testing is not possible without programming knowledge.

2)In automated testing, the test cases are executed by the software tools.
3)Automation testing is faster than manual testing
4)Automation testing takes up automation tools and trained employees
5)Exploratory testing is not possible in automation testing.
6)Automation testing uses frameworks like Data Drive, Keyword, etc.
7)Automated testing is more reliable due to the use of automated tools and scripts.
8)In automated testing, the test results are readily available to all the stakeholders in the dashboard of the automated tool.
9)Automated testing is conducted by automated tools and scripts so it does not involve assurance of user-friendliness.
10)Performance testing like load testing, stress testing, spike testing, etc.
11)Programming knowledge is a must in case of automation testing as using tools requires trained staff.
12)Automated testing is suitable for Regression testing, Load testing, and Performance testing.

Task 1:Testing methodologies and SDLC(Learners notes)

Amrutha p m — Sat, 09 Mar 2024 19:25:43 +0000

What are different types of testing?

1.Functional Testing :Testing which Focuses on the functional Aspects of the running application.Black Box ,Unit testing ,Integration ,Smoke,Sanity,UAT testing

2.Non functional testing :Testing which is mainly focusing on the Non functional elements such as UI design ,Compatability,Responssiveness ,Seccurity ,Performance etc.

3.White Box testing :Testing in which Tester should know the Internal structure of the application that runs.Mainly developer will do the white box testing sometimes Testers also in SDLC role.
Unit testing is one of the White box testing.

4.Black box testing : Testing in which Tester doesnt have the knowledge about the internal part.Tester only knows the inputs and outputs,testing conducted based on the expected outcome.User acceptance Testing is one of the Blackbox testing.

5.Grey box Testing : It is the combination of both black box and white box testing.Both end users and developer with partial knowledge of the source code.

6.Sanity Testing : It is a subset of UAT testing.It is done to ensure that code changes that are made are working as expected.IF any critical bug fixing is conducted sanity testing will be done immdediately.

7.Smoke Testing : It is a Rapid testing technique,used to validate whether the build is testable or not.or it can be used for further testing procedures.Subset of Regression testing.
End user as well as testers will do the smoke tests.
Black box is one of the smoke test.EX:Login Functionality of Irctc Website to book tickets.

8.Unit testing : It is done by athe developers and in some cases testers also. Basic leavel of testing.

9.Integration Testing : once the API integration is completed module wise Integration testing will conduct.Testers will do.

10.System Testing : Complete application will be tested based on the userstories or With its functional aspects.

11.Retesting : Retesting will be conducted during testing life cycle to ensure that the reported bug that have been fixed or not.

12.Regression Testing : It is done to ensure that the updations or code changes that are made doesnt effect the other functionalities or previously deployed part.

13.User acceptance testing :It is done by the end users or by the client according to their bussiness requirements.

14.Security Testing : It is done to ensure the vulnurabilities that are fixed to deliver a quality and customer satisfied product.

15.Compatibility Testing :It is done to ensure that cross platform browsing,compatible with different os versions and devices.

16.Performance Testing : Load testing ,stress testing etc.
It is done to make sure that the system is communicating friendly with larger scale customers and data without any crash.

Q2 .What are different STLC phases?

STLC stands for Software development Life cycle.

Phases:

Requirement analysis Phase Reviewing the SRS documentation and quality assurance team understands the requirements well like what is to be tested. If anything is missing or not understandable then the quality assurance team meets with the Development team/Bussiness Analyst/Tech Lead to better understand the detailed knowledge of the requirements. Identify the ambiguities, Identifying any missing or incomplete requirements, Identifying any missing or incomplete requirements, 2.Test Planning Identifies the objectives and scope of the test. Developing a test strategy like testing methods and techniques that will be used (agile method). Identifies the testing environment and resources needed. Identifies the test cases that will be executed.(RTM,Requirement tracebility matrix )and the test data that will be used. Estimating the time and cost required for testing. Identifies the test deliverables. Assigning the roles and responsibilities to the testing team, Reviewing and approving the test plan. 3.Test Case development Based on the requirement Tracebility matrix Test cases will be Mapped/prepared. The testing team also prepares the required test data/Scenarios for the testing. Test cases that are clear, concise, and easy to understand. Identifying the expected results for each test case. Reviewing and validating the test cases. 4.Test Environment Setup Once software test suites(Test cases) are designed, they need an interface to be executed in.This interface is called the Test Environment.It is created by integrating hardware,software,proper network configurations and data necessary to run tests. Mostly decided by the developer end or as per client requirement. 5.Test Execution In this phase testing team starts executing test cases based on prepared test cases. Once defect Logged in and FIxed by the developer Retest the same with test data and repot the result. 6.Test Closure Test closure stage is to ensure that all testing related activities have been completed and that the software is ready for release.And alsso it is to ensure that all relevent information related to testing that have been shared for future reference and enhancement.

4.As a manual Tester what qualities do you posses?Illuistarte with example?
For every business customer satisfaction is the main achievement.A quality product delivers this.so that a tester should have to analyse the things as a normal user along with the business goals to achieve.then only can deliver a quality product.
As a manual tester I should be best critic.
Good communication and good understanding of the current trends in the market.
Good logical and analytical problem solving skill.
Effective communication is the key thing to collaborate with the team and deal the situations and ideas within the team.then only can share different aspects of test deliverables
Testers communication skill helps to easy understanding of test cases and clear and presise defect report.
Example if the bug report is not easily understandable or confusing means developers can't fix the exact problem.chances to misunderstand the issues and there will arise a lack of communication.
Always be alert on testing example the design issues and keep testing to check their is any crash occurs .Continuos testing can only find out those minute but high severity issues.

*Q5.What is the difference between waterfall and agile methodologies?*

Waterfall model
1)The process is divided into specifict/Distinct phases.
2)Sequential development methodology.
3)Waterfall is a structured software development methodology so most times it can be quite rigid.
4)Software development will be completed as one single project.
5)There is no scope of changing the requirements once the project development starts.
6)All the project development phases like designing, development, testing, etc. are completed once in the Waterfall model.
7)The test plan is rarely discussed during the test phase.
8)In this methodology, the “Testing” phase comes after the “Build” phase.
9)Team coordination/synchronization is very limited.
10)Business analysis prepares requirements before the beginning of the project.

Agile model
1) It separates the phases into sprints
2)It involves incremental approach
3)Agile methodology is more flexible to work.
4)Agile can be considered as a collection of many different projects.
5)Agile is quite a flexible method which allows changes to be made in the project development requirements even if the initial planning has been completed.
6)Agile methodology, follow an iterative development approach because of this planning, development, prototyping and other software development phases may appear more than once.
7)Test plan is reviewed after each sprint.
8)In Agile methodology, testing is performed concurrently with software development.
9)Prefers small but dedicated teams with a high degree of coordination and synchronization.
10)Products owner with team prepares requirements just about every day during a project.

Task 2:Test case designs

Amrutha p m — Sat, 09 Mar 2024 19:04:20 +0000

Q1.You are testing a form that allows users to schedule appointments with the doctor. The form has the following fields : fisrt name , last name , email , phone number and appointment date and time .
Some more inputs:

If any field is blank , we should display “All fieldss are required”
If the email is invalid, we should display “please enter a valid email”
If the phone number is invalid , we should display “Please enter a valid phone number”
If the appointment date is not available, it should display “Please choose another date/time”
If all field are correct and the appointment is available , we should schedule the appointment successfully For these requirements write down the correct list of conditions in form of decision table

Answer

*Q2. Suppose you are a software tester and you are assigned to test a new mobile app that has just been developed. The app has three different user roles: basic user, premium user, and admin user. You have been given the following three test scenarios to execute:*

1)Basic users can only access limited features of the app, while premium users can access all features. Admin users have access to advanced settings and can perform all actions.

2)Users should be able to create and delete their accounts successfully. Passwords must meet the required complexity standards and users should receive a conformation email upon successful account creation.

3)Users should be able to navigate through the app seamlessly without any crashes or performance issues. The app should also display appropriate error messages when a user attempts to perform an action they are not authorized to perform.

For each of the test scenarios, describe the steps you would take to test them and the expected results.

Mobile App-Test Scenarios for users:
https://docs.google.com/spreadsheets/d/11F-5toyaATSsBalW4l6Jyc_Uii4j3CWgFOuPfk_HAXY/edit?usp=sharing