Manual Testing

What Is Software Testing?
Testing can be defined in simple words as “Performing Verification and Validation of the Software Product” for its correctness and accuracy of working. 
That means to find the Bug, Error, Defect, incorrectness in any application software.
A programmer makes an error (mistake), which results in a defect (fault, bug) in the software source code. If this defect is executed, in certain situations the system will produce wrong results, causing a failure.

Product Backlog
Product Backlog Product Backlog is the master list of all functionality desired in the product. A product or a project backlog is a prioritized list of requirements with a rough size and complexity estimate of each requirement. Hence, the backlog has 3 components: requirements, priority, rough size and complexity estimate.

* Master list of all “features”

* High priority features are split into “stories” achievable within an iteration.

* Each “story” is prioritized and scoped.

Sprint Backlog
The sprint backlog is the list of tasks that the Scrum team is committing that they will complete in the current sprint. Sprint Backlog is the set of Product Backlog items selected for the Sprint plus a plan for delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality.he Sprint Backlog is a highly visible, real-time picture of the work that the Development Team plans to accomplish during the Sprint, and it belongs solely to the Development Team.

High Level Design (HLD)
* List of modules and a brief description of each module.
* Brief functionality of each module. 
* Interface relationship among modules. 
* Dependencies between modules (if A exists, B exists). 
* Database tables identified along with key elements. 
* Overall architecture diagrams along with technology details. 

 Low Level Design (LLD)

* Detailed functional logic of the module, in pseudo code. 
* Database tables, with all elements, including their type and size.
* All interface details. 
* All dependency issues 
* Error message listings.
* Complete input and outputs for a module.

What Is Test Scenario?
* It’s a narrative story tell by user in which we think about ‘How end user use that product in real environment’. 
* Scenario test is a test based on hypothetical story used to help a person think through a complex problem or system

What Is Test Case?
* A set of test inputs, execution conditions and expected results, developed for a particular objective.
* Documentation specifying inputs, predicted results and a set of execution conditions for a test item. 
* The expected result specifies what the AUT should produce from the test inputs.

REQUIREMENT:

Business requirement: For business Prospective, What they Need In that product, that is Business requirement of the client.

Market requirement: For Making Clients Product better, we'll make survey in publicly to remove Drawbacks or ad some feature in apps, to improve the product quality.

Software requirement: All the Functionality Related To apps, what actually customer want in his software.