DEV Community: Hariprasath

TASK - 14

Hariprasath — Thu, 23 May 2024 13:58:11 +0000

Q-1-> What is the difference between automation and manual testing in software development?

Answer
Automation Testing

In automation testing, the test cases are executed by automated tools.
Automation testing is much faster than manual testing.
It requires automation tools and trained employees those have knowledge about coding.
It is more reliable than manual testing bcoz this testing is done by tools.
In sometimes, automation testing needs more investment than manual testing bcoz of automation tools.
Automation testing uses framework like data driven, testng, cucumber etc.
It is suitable for regression testing, load testing and performance testing.

Manual Testing

In manual testing, the test cases are executed by human resources.
Manual testing is consume more time.
It requires only human resources to execute the test cases.
It is not more reliable than automation testing bcoz human might make mistake in continuous work.
It is also needs investment to do testing.
Manual testing doesn't need frameworks.
It is suitable for exploratory testing, usability testing and adhoc testing.

================================================

Q-2-> Explore some of the most common automation testing tool available on the market?

Answer
There are many automation tools are running in the market. They are

Selenium
Appium
TestComplete
Katalon Studio
Cypress
Ranorex Studio
Perfecto
LambdaTest
Postman
SoapUI
Tricentis Tosca
Apache JMeter
Robot Framework
Applitools

Selenium
Selenium is still number one choice among the automation tester for web application. It is an open source and consists of selenium webdriver, selenium grid and selenium IDE.
Important Features:

It supports all programming languages like java, javascript, python, c, c++ etc.
It supports all browser as well so we can perform cross-browser testing.
Integration with other frameworks like Testng, Cucumber, Junit etc.

Katalon Studio
Katalon Studio is low code and scalable automation testing tool for web, mobile, API and desktop. It is available in both free and paid version.
Important Features:

Automatic retry failed tests, smart wait, and self-healing mechanisms.
Flexible methods for test design: record & playback, manual, and scripting mode.
Smart debugging UI and test reporting to troubleshoot failures quickly.

Postman
Postman is one of the most widely used automation testing tools for API. It allows users to write different kinds of tests, from functional and integration to regression tests, and execute them automatically in CI/CD pipelines via the command line.
Important Features:

Friendly and easy-to-use interface equipped with code snippets.
Support for multiple HTML methods, Swagger, and RAML formats.
Test suite creation, executions with parameterization, and debugging.

==================================================

Q-3-> What is the Cross Browser Testing?

Answer
Cross Browser Testing is a type of compatibility testing which comes under the non-functional testing. The aim of this testing is to ensure the application or software is working as intended when accessed through all browsers.
Different Browser:
Using different browsers like google chrome, firefox, microsoft edge etc. we should ensure the software is working properly through most of the browser.
Different OS Combination:
In desktop, there are different OS are available. So we have to test the software in most of the OS in desktop.
Different Device:
In Current world there are so much of mobiles devices came to competition. So that the software should work in most of the device. For that we are doing the cross browser testing.

================================================

Q-4-> Write a Blog on TDD and BDD?

Answer
Test Driven Development
Test Driven Development is a testing methodology or a programming practice implemented from developer's perspective. A developer writes an automated test case based on the requirements specified in the documents.
These tests are executed, and in some cases, they fail as they are developed before the development of an actual feature. The development team then re-factors the code for the test to pass successfully. TDD can be done by a single developer while writing both tests and application code side by side to complete a feature.

Benefits of TDD:

Reduces the amount of time required for rework.
Explores the bugs or errors very quickly.
Encourages the development of cleaner and better design.
Results in the creation of extensive code that is flexible and easy to maintain.

Behavioral Driven Development
Behavioral Driven Development is a testing approach derived from the Test-Driven Development (TDD) methodology. In BDD, tests are mainly based on systems behavior. This approach defines various ways to develop a feature based on its behavior.

Benefits of BDD:

Helps to reach a wider audience through the non-technical language.
Focuses on how the system should behave from the customer's and the developer's perspective.
It is cost effective technique.
Reduces the effort needed to verify the any post-development defects.

TASK - 5

Hariprasath — Mon, 29 Apr 2024 06:56:07 +0000

Scenario based questions:
Q-1-> Write as many test cases as you can for a given scenario using excel sheet. The excel sheet should include the following columns:

Test scenario ID(requirement matrix/user story): A unique identifier for each test case. for ex TS-1,TS-2.TS-3...TSn.
Test Scenario: A brief description of the test case.
Test case ID: A unique ID for testcase Forex: TC-1,TC-2,TC-3..TCn.
Test steps: A detailed list of the steps to be followed to execute the test case.
Input: The input of each step taken by user.
Expected results: The expected outcome of each step in the test case.
Actual results: The actual outcome of each step in the test case.
Pass/Fail: Whether the test case passed or failed.
Test Case Complexity.
Test Case severity.

Answer
https://docs.google.com/document/d/1rvxkVbUonndIqZy-UzfKjJd2CpaeLpdh9b2cNbo2rag/edit?usp=sharing

===============================================

Q-2-> Write the key points on test scenario, test case, test strategy and plan, test summary report.

Answer
Test Scenario
Test scenario is a documentation of test cases. It also called as test condition or test possibility. It is a description of any specific functionality or feature to be tested. Every scenario has unique id to track during testing. Mostly, Test scenario is written in one or two lines and approved by business analyst or team manager or lead.
Ex : TS_4 {verify the login functionality is working perfectly}

Test Case
Test case is set of actions or steps to perform the testing of any specific functionality. Every test case has unique id like scenario and mapped with their respective scenario. It contains expected result, actual result, steps, inputs and pass/fail. Test cases are more important than others in testing phase and it should be maintained by companies.
Example : TC_3 {verify the login with valid username and invalid password}

Test Strategy
The test strategy is a high-level document used to validate the test levels to be executed for the product. And it also describes what kind of technique has to be used and which module will be tested.The Test Strategy's main purpose is to deliver a systematic approach to the software testing process to ensure reliability, quality, traceability, and better planning.

It is derived with the help of Use Case documents, SRS (Software Requirement Specification), and Product Description.
A test plan is developed by Test Lead or test/ Project manager.
A test plan defines the whole testing activities thoroughly.
A test plan is a dynamic document that can be updated frequently when new requirements or modifications have occurred.

Test Plan
The test plan is a base of software testing. It is a detailed document, which includes several testing attributes such as test objectives, scope, test schedule, template, required resources (human resources, software, and hardware), test estimation and test deliverables, risk, mitigation plan, defect tracking, entry and exit criteria, test environment, etc.

While the Test Strategy can be derived with the help of the BRS (Business Requirement Specification) document.
Generally, the test strategy is developed by the Business Analyst and approved by the Project Manager.
It is a static document, which implies that it cannot be changed or modified.
The test strategy defines high-level test design methods.

TASK - 4

Hariprasath — Wed, 24 Apr 2024 17:24:52 +0000

Q-1-> Describe the difference in between:
1) Smoke and sanity testing

Answer
Smoke Testing

It is board approach where all parts of application are tested.
It is tested by either manual or automation testing.
It is performed by both developer and tester.
Smoke testing is the first test performed on the initial build.
It is considered as subset of acceptance testing.
Smoke testing is documented.
It is used in end to end function of application.

Sanity Testing

it is narrow approach where some specific parts of application are tested.
It is test can be done without scripts.
It is performed by testers.
Sanity testing is performed when the application is comparatively stable.
It is considered as subset of regression testing.
Sanity testing is not documented.
It is used to test the modified and bug fixed function.

==============================================

2) Verification and Validation

Answer
Verification

We check whether we are developing the right product or not.
Verification is also known as static testing.
Verification process includes like inspections, reviews nd walkthroughs
Quality Assurance is comes under verification.
Code of execution doesnt happen in verification.
Verification is performed by quality assurance team whether the product is developed according to customer's requirements.
It is performed before the validation process.
In verification, we can find the bugs early in the development phase.

Validation

We check whether the product meets the requirements or not.
Validation is also as dynamic testing.
Validation process includes unit testing, system testing, user acceptance etc.
Quality Control is comes under validation.
Code of execution is happens in validation.
Verification is performed by tester team whether the product is meets the BA's requirements.
It is done after the verification process.
We can find the bugs where they are not found in verification process.

===============================================

Q-2-> Explain about agile methodology.

Answer
An agile methodology is an iterative approach to software development. Each iteration of agile methodology takes a short time interval of 1 to 4 weeks. The agile development process is aligned to deliver the changing business requirement. It distributes the software with faster and fewer changes.
The single-phase software development takes 6 to 18 months. In single-phase development, all the requirement gathering and risks management factors are predicted initially.The agile software development process frequently takes the feedback of workable product. The workable product is delivered within 1 to 4 weeks of iteration.
A small group of peoples from agile developing the software is called agile squad.
There are five agile ceremonies conducted in agile by scrum master.

Sprint Grooming
Sprint Planning
Daily Standup
Sprint Review
Sprint Retrospective

=================================================

Q-3-> Explain about epic and user story?

Answer
Epic

It contains the large bodies of requirement, analysis, contents in few lines.
A single epic can broke into multiple stories.
Epic is a headline of automation scripts.
It is created by business analyst for developers and testers.
Example : Create a shopping website which is user-friendly and have multiple advance options in it.

User Story

It Contains small amount of content to develop and test in short period.
A multiple user stories becomes a single epic.
User story is sub-topic of Epic.
It is created by also business analyst for short term.
Example : Add voice command to the shopping website for easy access.

TASK - 3

Hariprasath — Wed, 24 Apr 2024 15:15:47 +0000

Q-1-> List down the all models of SDLC.

Answer

Waterfall Model
RAD Model
Spiral Model
V-Model
Incremental Model
Iterative Model
Big Bang Model
Agile Model

Waterfall Model
Waterfall is a model which is universally accepted SDLC model. It is a continuous software development process in which the development is seen as like flows steadily downfall through the different phases like requirement gathering and analysis, planning, developing, testing, deployment and maintenance.

Agile Model
Agile model is methodology which promotes continues developing and testing process in SDLC process. In this the entire project is divided into small phases which are called sprint. one sprint takes one or two weeks.

===============================================

Q-2-> What is STLC? Explain all stages of STLC.

Answer
The Software Testing Life Cycle is executed in well planned and systematic manner to improve the quality of the software

Requirement Analysis
Test Planning
Test Design
Environment Setup
Test Execution
Defect Tracking
Test Closure

Requirement Analysis
Requirement analysis is a process that analyzing the requirement given by business analyst. Knowing about that software through the requirement then only we can test the software perfectly

Test Planning
Planning the testing process before the development of the software is testing planning. Its a discussion about how much time it would take and how many sprint it would take & where will do it either automation or manual testing

Test Design
Test Design is important process in which we should test scenarios and test cases. Using test cases we can easily execute the testing process.

Environment Setup
Environment is a medium of test execution where we would test the software like in different browser, testing tool, etc. Those are setup in the process.

Test Execution
Executing the test cases written by testing team is called as test execution process. In the case testers are testing individually through automation or manual to ensure the quality of software.

Defect Tracking
If any defects or bugs are detected, we should take the proof of the defect and assign to that particular developer to clear the defects or bugs. this is called defect tracking

Test Closure
Tester should send the report to test lead or test manager. it contains all details like how many test cases and scenarios, defect, quality of software, duration of software etc.

===============================================

Q-3-> 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 you boss?

Answer
Quality Assurance-[QA]

Quality assurance is a group of activities which is used in during of development of software to ensure the quality of software.
The aim of quality assurance is to prevent the defects or bugs by paying attention to the process.
Quality assurance is proactive process. It concerns to improve the development so defects didn't arise.
QA is process oriented.
Each and every member of a development team should be responsible for this.
Example : Verification

Quality Control-[QC]

Quality control is a group of activities which is used in developed software to defect the defects or bugs.
The aim of quality control is to find the defects by paying attention to process.
Quality control is reactive process. It concerns to find identify the defects after development of software and before deployment.
QC is product oriented.
Testing team is responsible to this
Example : Validation

================================================

Q-4-> Difference between manual and automation testing?

Answer
Manual Testing

Executing the test cases one by one by manually using human resources.
There a more possibility to make error.
It takes more time and energy to do.
It require the high level of competence and experience to do perfectly.
It suitable for newly added features and functionality
It can be influenced by tester's knowledge of the software.
Its perfect for smaller projects.
Example : Testing the login functionality for the first time.
Automation Testing
Executing the test cases using automation tool and scripts.
It takes less time and energy compare to the manual testing.
It require the programming scripts and programming knowledge.
It suitable for testing the already existing functionality(regression testing).
It cant be influenced by tester's knowledge of the software.
Its prefect for the larger projects.
Example : Testing the already exists login functionality.

Automation Testing

Executing the test cases using automation tool and scripts.
It takes less time and energy compare to the manual testing.
It require the programming scripts and programming knowledge.
It suitable for testing the already existing functionality(regression testing).
It cant be influenced by tester's knowledge of the software.
Its prefect for the larger projects.
Example : Testing the already exists login functionality.

TASK - 2

Hariprasath — Wed, 24 Apr 2024 11:04:05 +0000

Q-1->.You are testing a form that allows users to schedule appointments with a doctor. The form has the following fields: first name, last name, email, phone number, and appointment date/time. Some more inputs:
• If any field is blank, we should display “All fields 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/time is not available, it should display “Please choose another date/time”
• If all fields 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
Decision table technique is one of the most widely used technique in testing to crack the combination of test cases. It contains set of combinations and their respective actions. It also known as cause-effect table.

Q-2->.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:
• 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.
• Users should be able to create and delete their accounts successfully. Passwords must meet the required complexity standards and users should receive a confirmation email upon successful account creation.
• 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.

Answer
The following scenario and their test cases are given below :-
Test Scenario 1

Test Scenario 2

Test Scenario 3

TASK - 1

Hariprasath — Fri, 19 Apr 2024 12:17:43 +0000

Q-1-> What are the types of Testing?

Testing is mainly divided into 2 types. They are manual testing and automation testing. Manual testing is classified into three types which are white box testing, black box testing and grey box testing.
In black box testing, it has 2 types, they are functional testing and non-functional testing. Unit testing, integration testing, system testing are functional testing and performance testing, security testing, compatibility testing are non-functional testing.

Q-2-> What are different phases in STLC?
Requirement Analysis, Testing Planning, Test Design, Environment Setup, Test Execution, Test Closure are the basic phases of STLC. It may differs on few companies.

Q-3-> As a manual testing, what qualities do you possess? Provide example to illustrate your points.

I am a manual tester, i need to know the software which is im going to test. For that i need good communication skills to know about that software and to clarify the doubts with developer. Quick learner, Creativity ideas to crack the software, patience, Passion to check the quality etc. As a fresher, Be friendly with others to gain knowledge.

Q-4-> What is the difference between waterfall and agile methodologies in SDLC?

In waterfall model, We have to wait for the completion of previous phase to start the next phase. It needs huge time to create the software. If we change any in between, have to start the project from first. Its only suitable for larger organization and long time project.
In agile model, The project spilt into small parts called as "Sprint". One sprint takes 2 or 3 weeks. So, we dont want to wait for previous phase to complete. We can change any changes in between the project. It saves more time and money so many companies using this methodology.