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