Scribd
Upload
13 views6 pages

Testing Notes 22

The document outlines various levels and methodologies of software testing, including unit, integration, system, and user acceptance testing, as well as testing types such as functional, non-functional, performance, security, and usability testing. It distinguishes between testing approaches like whitebox, blackbox, and greybox, and explains specific testing techniques such as smoke, sanity, retesting, regression, adhoc, and exploratory testing. Additionally, it discusses tools and practices for conducting these tests effectively, emphasizing the importance of application stability and user experience.

Uploaded by

suryavamshi825
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
13 views6 pages

Testing Notes 22

The document outlines various levels and methodologies of software testing, including unit, integration, system, and user acceptance testing, as well as testing types such as functional, non-functional, performance, security, and usability testing. It distinguishes between testing approaches like whitebox, blackbox, and greybox, and explains specific testing techniques such as smoke, sanity, retesting, regression, adhoc, and exploratory testing. Additionally, it discusses tools and practices for conducting these tests effectively, emphasizing the importance of application stability and user experience.

Uploaded by

suryavamshi825
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 6

Testing Levels:

unit testing: Testing done by developer on the individual components


integration testing: Testing done by developer after merging the code written by
different developers
system testing: Testing done by tester on all the application functionalities
system integration testing: Testing done by tester on the third party
applications/integrations if any
user acceptance testing: Testing done by client side team members

Testing Methodologies:
Whitebox Testing: Performing testing including/considering developer's code
Developers will do whitebox testing
Blackbox Testing: Performing testing without developer's code
Testers will do blackbox testing
Greybox Testing: Mixture of whitebox and blackbox testing
SDET will do greybox testing

Functional Testing: Performing testing on functional requirements which are


directly available to the end user/customer.
Non Functional Testing: Performing testing on non functional requirements which are
not available to end user/customer directly.

Performance Testing
Security Testing
Compatability Testing
Localization Testing
Usability Testing

Performance Testing: Checking the application performance

Load Testing: Performing testing to check how the application is loading with
different number of requests with minimum/neglegible delay.

Stress Testing: Performing testing to check at which point the server is getting
crashed or not able to handle anymore requests.

Volume Testing: Performing testing with differents storage capacities

Practically it is not possible to do performance testing. Using tools like load


runner and Jmeter we can go for performance testing.

Security Testing: Performing testing on the security level of the application


To do in full fledged security testing, we have penetration tool(Pen test)
But manually basic level of security testing can be done with the help of Protocal,
Authentication and Authorization
Protocal: The application URL should have https -> S stands for security
This is appended to http protocal after applying SSL(Secured Socket Layer)

Authentication: Validating the user to access the application/feature


Ex: Username and Password
Authorization: Validating the user's permission to do specific transaction

Compatability Testing: Performing testing on different operating systems with


versions and browsers with versions to confirm the application is working as
expected.

It it possible with the help of third party applications like Browserstack.

Localization Testing: Performing testing on language/currency conversions


Q: How localization testing can be done?
A: With the help of WVD(Windows Virtual Desktop), Remote Desktops

Usability Testing: Performing testing to check howmuch user friendly the


application is.
In this, we check for tooltips, tour guides, site maps, etc.

Functional Testing: Below are the ones to do functional testing


i. Field availability
ii. Field properties
iii. Business logic positive
negative
iv. End to flow happy path
non happy path

Website -> collection of web pages


webpage -> collection of web elements(fields)
Web elements -> textbox, label, image, button, link...

Smoke Testing: Performing testing on the application features whether it is


possible to do further testing.
It is a high level testing.
Smoke testing is performed to check if the application is stable or not

Ex: Let us consider in an ecommerce application - Registration, Login, Adding the


product to cart, Placing order
Smoke Testing:
i. Check if all pages are loading
ii. If able to add product to cart
iii. Required information is available to place order

Smoke testing will be done generally after receiving the release from development
team
(or) when the application is ready for testing

Sanity Testing: Performing testing on the application when moving from one level to
another level.
It is performed on stable build/application
It is indepth testing on specific features

Differences between smoke testing and sanity testing.


i. Smoke testing is performed to check the application stability where as sanity is
done on stable application
ii. Smoke testing is a highlevel testing but sanity is detailed testing
iii. Smoke testing focuses on all features but sanity focuses on specific features

Retesting: Performing testing again and again until the defect is closed
Retesting is done in below scenarios
i. When the defect is fixed by developer
ii. When the developer is rejecting the defect

When retesting is done after the defect fix, there are two possibilities
i. The defect may be fixed
ii. Still we can see the defect. In this case, reassign the defect to developer
Note: Retesting focus is on failed functionalities only.

Regression Testing: Performing testing on the existing working functionality after


the changes done by developer
Below are the scenarios to do regression testing
i. After the defects fixed by developer
ii. If there are any changes from client in that requirement

Adhoc Testing: Performing testing without any testing documentation


Requirements should be available to go for adhoc testing
To do adhoc testing, tester should have either past experience or good Knowledge on
application funtionality

Q: Did you perform adhoc testing in your career?


i. No, I did not get chance to work on adhoc testing
(or)
ii. Yes, I have involved in adhoc testing
Q: Did you identify any defects in adhoc testing?
i. Yes, I did adhoc testing when there is no required time for documenation. And I
identified around 5 defects
(or)
ii. No, I did adhoc testing when we had excess time. As I have covered every
condition in my testing document no new defects identified

Exploratory Testing: Performing testing with minimum documentation


This can be done when requirements are not properly available
Explore the existing application and gain knowledge on requirements.
Create an understanding document and use it for testing as reference

Q: Did you involve in exploratory testing


i. No, I did not get chance to work on exploratory testing
(or)
ii. Yes (give this ans if the project is upgrade project without proper
requirements available)

You might also like