DEV Community: saragini1

Task 4

saragini1 — Tue, 26 Dec 2023 17:51:37 +0000

Difference between Sanity and Smoke testing:

SANITY:

Sanity Testing is done by testers.
Sanity Testing verifies the new functionality like bug fixes.
Sanity testing is a subset of Regression Testing.
Sanity Testing verifies only a particular component.

SMOKE:

Smoke Testing is done by both developers and testers.
Smoke Testing verifies the critical functionalities of the system.
Smoke testing is a subset of acceptance testing.
Smoke testing verifies the entire system from end to end.

Difference between validation and verification:

VALIDATION:

Purpose:
Validation focuses on ensuring that the software meets the requirements and expectations of the customer.
Process:
It involves testing and validating the actual product.
Testing Type:
Validation is a dynamic testing process.
Execution of Code:
It includes the execution of the code.
Methods Used:
Black Box Testing, White Box Testing, and non-functional testing are used for validation.
Goal:
The goal of validation is to validate the actual product.
Timing:
Validation begins as soon as the project starts.
Defect Detection:
It can find bugs that could not be found during the verification process.
Responsibility:
Validation is executed by the testing team.

VERIFICATION:

Purpose:
Verification focuses on ensuring that the software correctly implements the specific function or feature.
Process:
It involves checking documents, design, codes, and programs.
Testing Type:
Verification is a static testing process.
Execution of Code:
It does not include the execution of the code.
Methods Used:
Reviews, walkthroughs, inspections, and desk-checking are commonly used methods for verification.
Goal:
The goal of verification is to validate the application and software architecture against specifications.
Timing:
Verification occurs before validation.
Defect Detection:
It can find bugs in the early stages of development.
Responsibility:
The quality assurance team typically handles verification.

AGILE METHODOLOGY:

Agile is a people-focused, results-driven approach that respects our rapidly changing world. It centers around adaptive planning, self-organization, and short delivery times, using frameworks like Scrum and extreme Programming. Whether in software development or other domains, Agile has proven successful for teams aiming to deliver value efficiently and collaboratively.

EPIC AND USER STORIES:

Stories:
also called “user stories,” are short requirements or requests written from the perspective of an end user.
Epics:
are large bodies of work that can be broken down into a number of smaller tasks (called stories).

Task 3

saragini1 — Tue, 26 Dec 2023 17:27:48 +0000

SDLC models:

Below is the list of different SDLC models:

Waterfall Model
V-Model
Incremental Model
RAD Model
Iterative Model
Spiral Model
Prototype Model
Agile Model

STLC and it's Stages:

STLC (Software testing life cycle) is sequence of specific tasks that are carried out in an order to evaluate the functionality of a software application and ensure that the application is defect free and validate that the business criteria is met.
The different stages of STLC are:

Requirement analysis:

This is the first phase of STLC life cycle, in this phase the testing team analyses and understands the client requirements and interacts with them incase more information is required to understand in detail about the application's functionality. In this phase the testing team prepares requirement traceability matrix and identifies the environment to execute the test cases.

2.Test Planning:
In this phase, Senior QA managers determine the test plan strategy, efforts, and cost estimates for the project. They also decide on resources, test environment, limitations, and the testing schedule.

3.Test case development:
In this phase the team comes up with all possible scenarios covering both positive and negative test cases in order to test the application

4.Test execution:
In this phase the team executes the test cases and logs defects based on the expected and actual results and verifies the bug fixes.

5.Test closure:
This is the last phase of STC where the team reviews test results, prepares test summary reports and provides QA sign off.

List of potential risk factors to consider for a web-based application:

Injection: Injection or SQL injection is a type of security attack in which the malicious attacker inserts or injects a query via input data (as simple as via filling a form on the website) from the client-side to the server. If it is successful, the attacker can read data from the database, add new data, update data, delete some data present in the database, issue administrator commands to carry out privileged database tasks, or even issue commands to the operating system in some cases.

2.Sensitive Data Exposure:
As the name suggests, this means that sensitive data stored is leaked to malicious attackers. This information can include personal data like name, address, gender, date of birth, personal identification numbers like Aadhaar card number or SSN, etc., financial data like account number, credit card numbers, health-related information, etc. This can result in a monetary loss if the attacker uses the financial information of users to carry out online payments (in most cases to cryptocurrency), identity theft, and reputation loss.

3.Using Components with Known Vulnerabilities
Most websites today depend on component-heavy development patterns, which means that in some cases it is possible that the development teams do not even know the internal working of the component. This means, if the component used is itself vulnerable to threats due to some broken code, incorporating it with your application can induce threat vectors as well. This also comes if you’re using older versions of the components or nested dependencies.

Difference between QA and QC:

Quality Assurance (QA):

It focuses on providing assurance that the quality requested will be achieved.
The aim of quality assurance is to prevent defects.

Quality Control (QC)

It focuses on fulfilling the quality requested.
The aim of quality control is to identify and act on fixing the defects.

Difference between Manual and Automation testing:

MANUAL TESTING:

In manual testing, the test cases are executed by the human tester.
Manual testing is time-consuming.
Manual testing doesn’t use frameworks.
Manual testing is not reliable due to the possibility of manual errors.
There is no need for programming knowledge in manual testing.

AUTOMATION TESTING:

In automated testing, the test cases are executed by the software tools.
Automation testing is faster than manual testing
Automation testing uses frameworks like Data Drive, Keyword.
Automated testing is more reliable due to the use of automated tools and scripts.
Programming knowledge is a must in case of automation testing as using tools requires trained staff.

Task 2

saragini1 — Sun, 24 Dec 2023 15:59:25 +0000

Decision table for filling a form for doctor's appointment:

User story Example :
An educational app is developed, it has three roles Basic, premium and Admin. Basic users can access only Demo class videos, Premium Users can access all demo and full course videos while, Admin has access to all videos and can upload the videos on the app.

Task 1:

saragini1 — Sun, 24 Dec 2023 14:19:30 +0000

Different types of testing

The literal meaning of testing is to check the quality, performance, reliability of (something), especially before putting it into widespread use.
In terms of technology, Testing means to check the quality of software application before releasing it into market.
Based on the purpose, scope, performance, level of software application, testing can be classified into different types.
Firstly, Testing can be broadly classified into two types:

- Functional Testing: Functional testing ensures that the functions and features of the application work properly. It is based on the business requirement and is easy to execute manually.
- Non-Functional Testing: Non-functional testing, on the other hand, examines other aspects of how well the application works, such as performance, scalability, and behavior 1. It is based on the performance requirement and is hard to execute manually.

Furthermore, based on the level of software application testing can be classified as:

- Unit testing: This type of testing is usually performed by the developers in the early level of application which focuses on testing the smaller units of code and its functionality
- Integration testing: It is performed after all the modules have been unit-tested. Integration testing helps to ensure that all components work seamlessly together as a single unit.
- Smoke testing: Smoke Testing is done whenever the new functionalities of software are developed and integrated with existing build that is deployed in QA environment It is a process that determines whether the deployed software build is stable or not. Smoke testing is a confirmation for QA team to proceed with further software testing.
- End-to-end testing: It is the process of testing the application from start to finish covering all functionalities of the application.
- Acceptance testing: It is a trial use of application before releasing it to end users.
- Performance testing: Performance testing is a testing technique that determines the speed, scalability, and stability of an application under a given workload.
- Sanity testing:Sanity testing is a type of software testing that evaluates the Critical functionality of a new software build. It is performed before full regression testing.
- Regression testing:It is a type of software testing that is conducted after a code update to ensure that the update does not affect the existing code.

Different STLC phases:

There are 6 stages of software testing life cycle:

Requirement analysis
Test planning
Test case Design
Test environment set up
Test execution
Test closure

Qualities of manual tester

1. Good knowledge of basic testing principles
example: A manual tester should know how to write test cases, execute them, and report bugs using a defect tracking tool.

2. strong Understanding of product requirements
example: A manual tester should be aware of all functionalities of the product such that they can write test cases covering positive and negative scenarios.

3. Test data management
example: A manual tester should be able to create test data that represents different user profiles, user roles, and user data.

4. Defect management
example: A manual tester should be able to report defects accurately, including details such as steps to reproduce, expected and actual results, and severity.

Attention to detail example: A manual tester should be able to identify small visual issues such as alignment, spacing, font size, and color discrepancies. They should also be able to spot logical errors, functional gaps, and usability issues that may impact the end-user experience.

Difference between waterfall and agile methodologies in SDLC

Waterfall

It is a linear sequential model to develop and test a software product.
The software development process is broken down into different phases.
In Waterfall model to make changes after one phase is difficult and costly.
There is very little client involvement and very little feedback is taken.
Its delivery time is very long, the entire project must be completed before delivery.

Agile

It is a continuous iteration life cycle model to develop and test a software product.
In this the entire process of development is divided into sprints
Agile development model is flexible to make changes at any point of time (or at any stage of development process)
Continuous client Interaction and feedback
Its delivery time is very short and functional software is available very quickly.