Google Spreadsheet - How to insert a new sheet to google spreadsheet.

Google spreadsheet supports having multiple sheets in every spreadsheet just like in excel sheets. It is helpful to have different sheets added to the spreadsheet to maintain data for different features during testing. We can have each sheet named accordingly so that it is clearly readable. Let's start by learning how to add a new sheet to a worksheet

Add Sheet
Click on Add Sheet button which is in the bottom left corner of the screen. Once you click on Add, a new sheet is added with the default sheet name and number.

Duplicate Sheet
Sometimes, you may be required to keep the formatting of the sheet the same throughout, rather than formatting every sheet on creating it, just duplicate the sheet to keep the formatting. Delete the unwanted data and you are good to go. 

Insert Tab or Use shortcut Key

You can also insert a new sheet using the Insert tab. Note that you can use SHIFT + F11 to create the new sheet too. 

Let me know if there are any other ways to do it. Happy Spreadsheeting :)

Series Numbering in Google Spreadsheet

Whenever you create a new google spreadsheet it is better to have series numbering listed for each row in column 1. We already have numbering before the 0th column but, if you have a huge pile of data and if somebody asks to check the 1000th row then you can directly search for 1000 in the search to highlight the particular row. Below, I have mentioned different ways to add series numbering in google spreadsheets.

1. Manual: Entering numbers in each row.

2. Use the drag action: Enter the number 1 in the first row of the column(A1) and then add number 2 in the second row of the same column (A2), then point the cursor to the right bottom corner of the number 2 cell to get a + symbol. Now click on it and drag the cursor below to automatically add the number.

3. Incremental Formula:
Add number 1 in the first row of the first column (A1), now in the 2nd row of the first column add the formula as below.

=(A1+1)

Now drag the cursor of the 2nd row below to automatically add the numbers.

Consider you have a scenario where you have to count the number from in between say 1000 then, just change A1 to 1000, it will auto-increment from 1000. Try it.

4. ARRAYFORMULA: Consider you want to add numbers till 1000 rows, it will be quite tiresome to use the dragging cursor action or incremental formula dragging. Although you can do it if you have an ample amount of time, there is an easier way to add the auto numbering to any row. You can use ArrayFormula formula to automatically add the numbers in the sheet. Below is the example to add 5 rows with incremental numbers using ARRAYFORMULA

=ARRAYFORMULA(ROW(A1:A5))

Add the above formula to row A1 and hit enter.

If you want to add numbering till 100 then you just need to change the formula to below

=ARRAYFORMULA(ROW(A1:A100))

Note:

1. If you delete any row from the numbered row then you can observe that the numbering will not be affected, this is not the case when using manual numbering or drag action. Also observe that the formula dynamically changes to A1:A99. Try it.
2. If you want the series numbering to happen for columns then you need to change the formula as

=ARRAYFORMULA(Column(A1:1))

Fun Fact: 
1. You can add 5000000 rows keeping only 1 column in the sheet. I was extremely bored on a Quarantine Sunday and I tried adding 5000000 entries in the sheet to check if the browser would crash. It did a couple of times. Find the google spreadsheet below. Don't blame me if your system gets hanged :D

https://docs.google.com/spreadsheets/d/1TbF7t1Vg18LzHQjGjA72a0-oMbFiwULNG4svVLuSXKg/

2. You can add 18278 columns in one spreadsheet if you keep only 273 row in the sheet. As mentioned previously I tried adding the columns to test how it behaves. Click the link below.

https://docs.google.com/spreadsheets/d/11Yl4Fpg7UXvhNVq9iXVPy6t1UQbi_qK0U9Eh5LVVq8I/

I will make another post for filling sequential text and much more in the coming blog posts.

Google Spreadsheet Introduction - Understanding the spreadsheet

Google spreadsheet has many features which can be used for day to day QA tasks, before moving to how to insert data and formulas to the sheet, let us first understand terminologies which are used in google spreadsheet. If you have not gone through my post on how to create a new google spreadsheet then visit the link below first.

Link: https://qualitytestingtips.blogspot.com/2020/04/google-spreadsheet-introduction.html

Let's start with the most import terminologies used in the spreadsheet. 

Worksheet( Sheet)

Every page in the spreadsheet is called Sheet.

Cell:

Every box in the google spreadsheet is called a Cell.

Rows:

Horizontally displayed cells are called as Row. Rows are represented by numbers on the Y-axis.

Columns: 

Vertically displayed cells are called as Column. Columns are represented by Alphabets on the X-axis

Google Spreadsheet Introduction - Creating a spreadsheet

Google Spreadsheet is a web-based application that was introduced by Google in the Year 2006. Google acquired the software from 2Web Technologies which had originally created the idea of online-based spreadsheets. Google spreadsheet is available in all the browser platforms and as a mobile-based application too.

Google Spreadsheet is a boon to every QA who likes to maintain proper documentation while testing. Earlier I used to use excel sheet for all QA tasks, but I realized that google spreadsheet is much better when you need to share it to different QA's who are required to edit the sheet. It saves time as multiple users can edit the file in the same session. I just have 2 and half years of experience but I am going to make sure I clearly explain each formula with different examples in the coming posts. I would also explain how with simple Javascript knowledge, you can be a better google app-script QA.

Understanding how to access Google Spreadsheets is also necessary if you have never used google spreadsheets. Below are the steps to create a new google spreadsheet.

1. If you have a Gmail account then you can access the google drive by clicking on the link below

Link: https://drive.google.com/drive/u/0/my-drive

If you do not have a Gmail account then you need to create one to access it.

2. Click on the New button.

3. Click on Google Sheets 

4. Voilà! You have successfully created a new google spreadsheet. Congratulations :)

5. You can name your Spreadsheet by clicking on Untitled spreadsheet

6. Type any name as you wish, I have named my spreadsheet as Teaching Google Spreadsheet

Fun Fact: You can add 9500 characters to the name field. But, I have crashed the browser by continuously adding around 2 Lakh characters :D

How do you install an iPa file in iPhone using Xcode software?

iPa file can be installed in iPhone/iPod/iPads using Xcode software in mac system instead of using iTunes application.

Steps to Install the iPa file.

1. Open Xcode application.

2. Under Windows tab you will find Devices option

3. Click on Devices

4. Connect your iPhone/iPod/iPad to the mac system

5. Drag and drop the iPa file under Installed apps

Make sure that the provision profile is updated with the UDID of the device.

Different type of performance testing in software testing.

Listed below are the types of performance testing

1. Load testing: Load testing is a type of performance testing where increasing amount of load is applied to the system to check how the application performs till the threshold limit is reached.

Ex: Consider the system can handle only 1000 users in an application. Initially 10 users are injected and gradually the amount of users are increased till it reaches the threshold of the system i.e 1000 users to check how the system performed under various injected users.

2. Stress testing: Stress testing is a type of performance testing where the amount of load is increased more than the threshold limit in-order to break the system and to check how the application performs.

Ex: Consider the system can handle only 1000 users in an application. More than 1000 users are injected to the system in-order to break the system and to check how the application would respond

3. Volume testing: Volume testing is type of performance testing where particular amount of load is applied to the system to check how the application performs.

Ex: Consider the system can handle only 1000 users in an application. System is tested for 500 users or 900 users to check how the application performs.

4. Soak testing: Soak testing is a type of performance testing where the system is tested over a significant period of time by applying significant load to check how the application behaves.

Ex: Keeping an application for overnight while the data is injected to the system. Consider you have a new application which refreshes the page every-time a new news is added. Keeping the application open and injecting news to check how the application performs.

5. Spike testing: Spike testing is a type of performance testing where the load is suddenly increased and decreased and vice-versa to check how the application performs.

Ex: Consider the system can handle only 1000 users in an application. Load of 900 users is applied and suddenly the load is brought down to 100 and vice versa to check how the system performs

6. Scalability testing: Scalability testing is a type of performance testing where the system is tested once the load of the system is increased to meet the growing need

Ex: Consider the system can handle only 1000 users in an application. Now due to the application is getting used by more than 1500 in an year the system is now made to handle 1500 users.

Resolutions of all Apple products

QA's should always have the resolution list by-heart as it would be helpful when asked either in meeting about a resolution of the device or during scrums. It's kinda easy to remember it if your remember the base resolution and apple devices are limited when you compare to Android. I know that some people would be "A google search would let you know the resolution of the device", but I feel this would be useful when you go for an interview too.

iPhone	Resolution
iPhone 1	320*480
iPhone 3G
iPhone 3GS
iPhone 4	640*960
iPhone 4S
iPhone 5	640*1136
iPhone 5s
iPhone 5c
iPhone Se
iPhone 6	750*1334
iPhone 6s
iPhone 7
iPhone 8
iPhone 6s Plus	1080*1920
iPhone 7 Plus
iPhone 8 Plus
iPhone X	1125*2436
iPhone Xr	828*1792
iPhone Xs Max	1242*2688

Important testing questions which can be asked during interviews

I have listed few of the manual interview questions which can be asked for fresher to mid level QA's.

1. Explain Stub?
- Stub is a substitute for actual code when top down integration is conducted.

2. What do you mean by a driver?
- Driver is a substitute for actual code when bottom down integration is conducted.

3. Explain Big Bang Integration?
- When all the modules are integrated together then it is called as Big Bang Integration.

4. Explain Retesting and Regression testing?
- Retesting is a type of testing which is carried out to test the defect which was found in the previous build and to verify if the defect is fixed.
- Regression testing is a type of testing which is carried out to test the whole module in which the defect was fixed i.e. all the test cases of the module are run along with the defect fixed to check if the defect which was fixed has affected any other functionality.

5. Explain Smoke and sanity testing?
- Smoke testing is a type of testing which is carried out to check if the major functionality of the application is working as per the spec. A smoke test plan checklist is run to check if the build can be further tested.
- Sanity testing is type of testing which is carried out to check if all the functionality are working fine after minor fix of defect is conducted or when moving to a new environment.

6. Explain the difference between Latent and Masked defect?
- Latent defect is a defect which is found in the current release but the defect was introduced in the previous releases.
- When a defect is hiding another defect then the hidden defect is called as Masked defect.

Explain STLC

STLC stands for Software Testing Life Cycle. STLC is a process which is executed in a sequence in order to reach quality goals. STLC has different phase as SDLC. Following are the phases of STLC

1. Requirement gathering and analysis
2. Test Planning
3. Test Case Development
4. Test Environment Setup
5. Test Execution
6. Test Closure

Abbreviations for Mobile Applicaiton Tester

Abbreviations which are required to be kept in mind while giving interview for Mobile application testing

iPa - iPhone Application Archive

apk - Android application package

exe - Executable file

adb - Android Debug Bridge

CMMI - Capability Maturity Model Integrated

QA - Quality Assurance

QC - Quality Control

STLC - Software Testing Life Cycle

SDLC - Software Development Life Cycle

Risk Management in Software Testing with example

Software company should always have a risk management done so that there will be smooth release of the product. Risk management is divided into 3 main parts.

1. Risk Identification
2. Risk Impact Analysis
3. Risk Mitigation

Risk Identification
Risk identification will be the first step of risk management where the QA manager or the QA lead would identify all the risk which could be involved in the project which would impact the project plan

Examples of Risk Identification

- Non availability of test environment or logistics
- Critical defects found during the release state
- Non availability of testing resources
- Requirement or design changes
- Natural calamity
- Understand of technologies

Risk Impact Analysis
QA manager has to prioritize the risk based on the probability of occurrence and impact due to the risk. Taking the same example of risk identification we can prioritize the impact as shown below

- Non availability of test environment or logistics  - Probability Low, Impact High
- Critical defects found during the release state - Probability Medium, Impact High
- Non availability of testing resources - Probability Low, Impact Medium
- Requirement or design changes - Probability Low, Impact High
- Natural calamity - Probability Low, Impact Medium
- Understand of technology  - Probability Medium, Impact High

Risk Impact can be shown in percentages or scale from 1-10

Risk Mitigation
QA manager should be having solutions to every risk that may occur. Solution needs to be practical and should be always be in a state of executing the solutions in a way it is mentioned i,e, Risk mitigation should not give false promises

- Non availability of test environment or logistics - Have a quick meeting with the customer and get him/her to provide a list of devices and test environment which would be their highest priority for the release
- Critical defects found during the release state - If a critical defect is found during the release state then have an experienced working developer and a Qa to just work on the defect and have it regressed quickly as possible
- Non availability of testing resources - If a Qa gets sick or if he leaves the company then have a back up Qa from start of the project where he will be briefed with the project requirements and his involvement will be less than 10%
- Requirement or design changes - Customer has to be formally informed that no changes will be entertained without pushing the release dates and if there is any changes then it would be taken as a Change Request with efforts breakdown
- Natural calamity - A backup resource would be provided in another location and will be assigned with the task if any Natural calamity occurs.
- Understand of technology - Training will be provide and a team which has already released a similar project will help before the project reaches the first alpha.

Adhco testing in Software testing

Adhoc testing is a type of black box testing which is carried out without following any formal process i.e without SRS, Test plan or test cases. Adhoc testing is normally done once the formal test cases are run and testing is completed formally. There are 2 types of Adhoc testing

1. Paired Testing
2. Monkey Testing

Paired testing is type of adhoc testing where two qc's are assigned to test the same project and the goal of the qc's is to find maximum number of defect such that the test coverage is complete. Once the testing is completed both the qc are required to share their observation. Sometimes a qc is paired with the developer to perform adhoc testing which is proved to be a best adhoc type of testing as the developer will also be able to understand how a qc thinks out of the box. But normally it is not advisable if the project is working under scrum.

Monkey testing is done by performing unusual scenarios in order to break the code. Example: Continuously tapping on button, performing immediate sequence, adding inappropriate data as a value.

Waterfall model

Waterfall model is believed to be the first software method to be used in software development. This model follows a procedure where next phase of cycle is started only when the previous phase is completed. This model can be used for small scale project and mainly if there is no uncertainty in the software requirements. Waterfall model is also called as linear sequential life cycle model. Waterfall model may not be applicable to today's world as requirements are dynamic and keep changing as a phase is completed.

As word suggests, it flows downwards with phase mentioned below.
1. Requirement Analysis and Gathering:
2. Design
3. Implementation
4. Testing
5. Deployment
6. Maintenance

Pros and Cons of Waterfall model

Pros

- It is easy to understand and manage
- Since the requirements are frozen there would be no confusions and phase can be carried out in ease
- Product can be delivered on time as each phase would be assigned with efforts and there would be no rescheduling the efforts or dates

Cons
- If a defect is found during testing phase then it becomes difficult to get back to development stage and change the entire set of code or logic
- Next phase team especially testing team would be idle until the implementation phase is completed unless they are made to test some other project
- Clients will be only able to check the working condition of product only when the implementation is completed

List out different software methodologies in software testing.

Below are the some of the software methodologies used in software testing.

1. Agile model

2. Waterfall model

3. V model

4. Incremental model

5. Iterative model

6. RAD model

7. Spiral model

8. Prototype model

What do you mean by latent and masked defect?

Latent defect: Latent defect is a defect which is not found for a long time i.e. the defect is discovered now even though it existed way before the present version.

Masked defect: Masked defect is a defect in which a defect is hiding another defect.

Difference between mobile application testing and web application testing

Mobile application testing	Web application testing
- Testing is carried out by installing a executable file i.e. .apk for android and .iPa for iOS	- Testing is carried out on a URL over the internet on a browser
- Testing in different devices with different resolution	- Testing on different browsers with different resolution to check the responsiveness
- Testing in different network - 4G, 3G, 2G and Wifi	- Testing on broadband connection and Wifi connection
- Testing on Different OS - iOS and Android	- Testing on different OS - Windows 10, Windows 8, Windows 7, Mac
- Testing notifications, install uninstall application, test for battery consumption, test for memory consumption and leaks, interruption of calls and SMS
- Test for network disconnections and check if proper errors are shown
- User interaction can be from single tap to multiple taps	- User interaction is mainly using Keyboard and Mouse

What do you mean by Soak Testing?

- Soak testing is a type of testing where the system is tested over a significant period of time by applying significant load to system to check how the system behaves.

- Soak testing is also called as endurance testing.

- Soak testing is a type of performance testing.

- Soak testing is a non functionality testing.

- Soak testing is carried out to check the memory leaks in the system.

Ex: A system may perform well on calculating the tax of n person in an hour. If calculating the tax of n number of person in 24 hours along with the checking of balancing sheet of bank would result in checking of the endurance of the system or performing soak testing.

Difference between Smoke and Sanity testing

Smoke	Sanity
Smoke test is performed to check if the major functionalities as proposed  in the requirement document is working as expected or not before starting system or regression testing.	Sanity test is performed after system or regression testing is carried out to ensure that major functionalities are working as expected and not broken.
Smoke test is build verification testing	Sanity test is build acceptance testing
Smoke test is carried out to check all the major functionalities of a product. If smoke test fails then the build is declared as unstable and testing is stopped.	Sanity test is carried out to check on  a limited functionalities of a product.

Difference between Verification and Validation

Verification	Validation
Verification is process of ensuring that the product is being build according to the requirement and design specification	"Validation is a process of ensuring that the product is built according to the user need and business requirement"
Verification is "Are we building the product right?"	Validation is "Are we building the right product"
Verification is done before the development phase	Validation is performed after the development phase

Difference between Retesting and Regression testing?

Retesting	Regression
Retest is carried out when a particular defect is fixed and tester has to run through the test cases related only to the defect fixed	Regression testing is carried out to check if the defect which is fixed in the module has affected any other module or not. Here tester has to run through the whole module i.e. the test cases which are already passed too and not a particular test case.
Retest is carried out to check if the prior defect which is logged has been rectified.	Regression testing in laymen term is to check if there are any side effect to the defect fixed.
Retest is a planned testing	Regression testing is generic testing