The article about sprint retrospective activities in agile method. This is very important process in the scrum framework and useful in practical work experience.
This article about Scrum artifacts such as: Product Backlog The requirements for the product are listed in the Product Backlog. Always changing, dynamically prioritized list of requirements ordered by Business Value. Burndown Chart The Burndown chart shows the amount of work remaining per Sprint. Sprint Backlog The Sprint Backlog contains all the committed User Stories…
The article will helps you to aware all scrum process activities in agile. Also the use of scrum frame work and introducing sprint activities. let start
This article about client server testing. before start characteristics of client server testing architecture, you will read some of details about architecture and client/server process.
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.
Here we will see more details on Entry and Exit criteria in the across the testing activities and also will go through point to point description for both criteria. This port most of the all fresher and experience people can use for their practical work and I have provided sufficient practical experience.
The article about traceability matrix with useful information as what actual traceability, use of traceability matrix in the testing phase, how to develop traceability matrix and use of traceability matrix.
Verification is the confirmation that the product meets identified specifications. Checks for uncovered requirements. Validation is the confirmation that the product approximately meets its design functions (User requirements). Checks or executes functionality.
This article will helps you to aware all the software testing definitions which comes across the manual testing, the definitions are in very simple word to understand.