RSS

Tag Archives: mobile test cases

Verification and Validation


 Verification and Validation.

  • Testing is part of verification and validation.
  • Verification: Are we building the product right?
  • Validation Are we building the right product?
  • V&V activities include a wide range of the SQA activities.
kevalshah.in

Read the rest of this entry »

 

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Some Important terminologies


Some Important terminologies

  • Project :  If something is developed based on a particular user/users requirements, and is used exclusively by them, then it is known as project. The finance is arranged by the client to complete the project successfully.
  • Product :  If something is developed based on company’s specification (after a general survey of the market requirements) and can be used by multiple set of masses, then it is known as a product. The company has to fund the entire development and usually expect to break even after a successful market launch.
  • Defect v/s Defective: If the product is justifying partial requirements of a particular customer but is usable functionally, then we say that The product has a defect, But If the product is functionally non usable , then even if some requirements are satisfied, the product still will be tagged as Defective.
  • Quality Assurance : Quality assurance is a process of monitoring and guiding each and every role in the organization in order to make them perform their tasks according to the company’s process guidelines.
    kevalshah.in

    Read the rest of this entry »

 

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Definitions of Black-box and White-box Testing


Black-box: This testing methodology looks at what are the

available inputs for an application and what the expected outputs are that should result from each input. It is not
concerned with the inner workings of the application, the process that the application undertakes to achieve a
particular output or any other internal aspect of the application that may be involved in the transformation of an
input into an output. Most black-box testing tools employ either coordinate based interaction with the applications graphical user interface (GUI) or image recognition. An example of a black-box system would be a search engine.You enter text that you want to search for in the search bar, press “Search” and results are returned to you. In such a case, you do not know or see the specific process that is being employed to obtain your search results, you simply see that you provide an input – a search term – and you receive an output – your search results.

kevalshah.in

Read the rest of this entry »

 

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Evaluating exit criteria and reporting


Evaluating exit criteria is the activity where test execution is assessed against the defined objectives. This should be done for each test level, as for each we need to know whether we have done enough testing. Based on our risk assessment, we’ll have set criteria against which we’ll measure ‘enough’. These criteria vary for each project and are known as exit criteria. They tell us whether we can declare a given testing activity or level complete. We may have a mix of coverage or completion criteria (which tell us about test cases that must be included, e.g. ‘the driving test must include an emergency stop’ or ‘the software test must include a response measurement’), acceptance criteria (which tell us how we know whether the software has passed or failed overall, e.g. ‘only pass the driver if they have completed the emergency stop correctly’ or ‘only pass the software for release if it meets the priority 1 requirements list’) and process exit criteria (which tell us whether we have completed all the tasks we need to do, e.g. ‘the examiner/tester has not finished until they have written and filed the end of test report’). Exit criteria should be set and evaluated for each test level. Evaluating exit criteria has the following major tasks:

kevalshah.in

Read the rest of this entry »

 

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Test Strategy Template


These are the most common sections:

1.Objectives
State the objectives of this document at a high-level.

2.Scope
State the scope of the testing strategy, what will the testing concentrate around, at high-level; leave details for the Testing Scope.

3.Test Deliverables
State the testing activities and what documents result from these activities; for example a testing activity is Test Planning and the document resulting is the Master Test Plan or Test Plan.

4.Testing Schedule
Give the timelines around which the project is planned and where testing fits in this schedule.
I find that a diagram has a high-impact on the user (a Georgia rule of thumb is that I use color and diagrams to break the boredom of the text).
Describe the diagram in words.

5.Test Scope
The Project Charter or Master Test Plan usually state all the items in scope, just copy and paste from these documents. Add anything that’s missing or has changed from the last review.
Then state any items that are Out of Scope.

6.Risk Analysis
State all the risk that you envision, the higher the risk – the higher the test priority.
When you start testing you will want to start with the high-priority items, then test medium-priority and if time permits test low-priority functionality.Risk Analysis is very important from this point of view because it drives the whole test strategy. When giving the risk state how to you plan to mitigate (to alleviate, to make less severe) and what is the contingency plan (back-up plan in case this happens).Additionally you may want to say what is the impact of each risk.

kevalshah.in

Read the rest of this entry »

 

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

System Test Strategy Template



Provided by Rex Black Consulting Services

  1. Product, Revision and Overview

Describe the product and revision designator.

Describe briefly how the product works. Reference other material as appropriate.

  1. Product History

Include a short history of previous revisions of this product. (3-4 sentences). Include defect history.

  1. Features to be tested

List all features to be tested. Organize the list in the way that makes most sense- user features, or by level:

Application
Demo software
Client substrate
Server
Network (this may be more layers)
  1. Features not to be tested

Describe any features not to be tested

  1. Configurations to be tested and excluded

I recommend a table showing which hardware configurations will be tested with which software.

  1. Environmental requirements

Enumerate hardware, firmware, software, networks, etc. required to carry out the testing.

  1. System test methodology.

Brief description of work items to be performed from the beginning to the end of the product development.

  1. Initial Test requirements

Test strategy (this document), written by test personnel, reviewed by product team, agreed to by project manager.

  1. System test entry and exit criteria
kevalshah.in

Read the rest of this entry »

 

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

test case format -sample


unique-test-case-id: Test Case Title

Purpose:

Short sentence or two about the aspect of the system is being tested. If this gets too long, break the test case up or put more information into the feature descriptions.

Prereq:

Assumptions that must be met before the test case can be run. E.g., “logged in”, “guest login allowed”, “user testuser exists”.

Test Data:

List of variables and their possible values used in the test case. You can list specific values or describe value ranges. The test case should be performed once for each combinationof values. These values are written in set notation, one per line. E.g.:loginID = {Valid loginID, invalid loginID, valid email, invalid email, empty}password = {valid, invalid, empty}

Steps:

Steps to carry out the test. See step formating rules below.

  1. visit LoginPage
  2. enter userID
  3. enter password
  4. click login
  5. see the terms of use page
  6. click agree radio button at page bottom
  7. click submit button
  8. see PersonalPage
  9. verify that welcome message is correct username

Notes and Questions:

  • NOTE
  • QUESTION
kevalshah.in

Read the rest of this entry »

 

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

 
%d bloggers like this: