We already seen many test cases belong to different domains however here I am going to describe some of sample test case for banking application on testingnotes, so that you can refer in your projects. Sample test case for banking application before test case we can see some basic domain knowledge about banking, which traditional…
Category: Manual Testing
The article brings you to increase your passion about notes on exploratory software testing. This is my second session on exploratory testing.
The article brings you to increase your passion about exploratory software testing. This is my first session on exploratory testing.
This article helps you to increase your knowledge on priority and severities. Also I have shared all practical examples of priority and severity in software testing.
The article about Defect severity levels in software testing, which assigns to created new defect report. This article very informative and useful to beginners who’s going to start their career in the software testing.
The article about practically how to create defect report in TFS, and it is very useful to beginners who’s going to start using team foundation server in their organizations. This is real industry knowledge, I am going to share with you.
The article helps you to know as what are the parameters of defect report in software testing, also purpose of this article to share my practical industry experiences with all of you.
The article about How to write test cases in excel sheet. This article complete written based on practical industry experiences. It will help you to crack your interviews.Moreover, we will also cover topics like test case template, test case example (test cases for pen), test plan template, test scenario (test scenario template), testing life cycle…
As you read thoroughly all testing types, now this article is about Sanity Testing and Smoke Testing which are the important testing after application build received. Also the I have mentioned some of difference between Sanity and Smoke testing.
Methods of Validations: White Box Testing: Based on knowledge of the internal logic of an application’s code. Tests are based on coverage of code statements, branches, paths, conditions. Black Box Testing: Not based on any knowledge of internal design or code. Tests are based on requirements and functionality.