Amazon offers

Software Test cycle

Requirements analysis
Checking for the number of Modules in the requirement document
Preparing requirement traceability matrix and checking for the sufficiency of the requirements
Gather the doubts about the requirements from the document and getting them clarified from the client
Test plan preparation
Preparation of functional test requirements
Dividing the test requirements into test cases
Checking for the data required for the test case
Classifying the test case into small or medium or complex
Calculation of the time and effort required for the test case
Test effort estimation
Classification of test cases into small, medium and complex
Analyzing the time and effort required based on the type of test case.
Test case preparation
Preparation of test case title, steps to execute, gathering data for the test case if required, expected result and actual result.
Test case execution
Checking if the test environment is perfect by doing smoke test. Then proceeding for the test execution.
If the smoke test is success. Executing the test case as the steps to execute are written.
If the smoke test failed. Reporting the high severity error immediately after thorough checking and proceeding after confirmation received from the client.
Making note of the defects in the defect tracking tool along with the
i. Image if possible
ii. Actual steps executed
iii. Actual result occurred
iv. Data used for testing
v. Number of occurrences of the defect
vi. URL if possible
Defect management
Making note of the number of defects along with URL, environment, date, time, and number of defects and person who produced the defect.
Defects should be reported to the client and should be declared as bug when confirmed as defect.
Provide a severity and priority to the bug and assign it to the correct developer based on client’s instructions.
Try to reproduce the same bug in the next environment based on client’s instructions.
Change the status of the bug accordingly and the person to whom it should be assigned.

Comments

Post a Comment

Popular posts from this blog

Input Data Validation

Every web application is expected have at least one submit form. Data entered in form is transferred as input to database or to any other application and will decide the output. So, input data plays a very important role in retrieving the output data. Such data needs to be validated by the code. And tester has the responsibility of validating such data. At this point tester thinks about how can the validations be done and what type of data should be provided to validate the input field. Test data needs to be created and passed to the form through the automation tool or manually. Here are few steps or guide lines to validate the data. Let’s consider a sample form which acts as input to signing in as new member in a social networking site like facebook. It contains different types of input fields – Numeric, String, Alpha Numeric, date, preset values (from drop downs or check boxes), file uploads and Email addresses. Name: String input field Password : Alphanumeri
Read More

How to test search functionality

Every web application by default will contain search feature in it. Many search engines’ main functionality is search feature. The parameters to be considered while developing this feature or testing this feature are not limited. There are many factors which should be looked in when checking the coverage and usability of the search text box in the application. Preparation before testing the search functionality 1.        Note down the valid input details for the search feature. 2.        Find out the minimum and maximum range. 3.        Find out the depth of the search – document search, word in a document, image search 4.        Should document search display the size of the document also? Similarly for image? 5.        Any advanced search features like document or image type selection to refine the search are available? 6.        General set of input which can be given are a.        A-Z b.       a-z c.        0-9 d.       {      [              (       
Read More

Scrum Methodology - Quick Info

Image
It is one of the unique methodologies of agile methodology. Scrum  It is an   iterative, incremental   framework for project management . It   is a loose set of guidelines that govern the development process of a product, from its design stages to its completion. It aims to cure some common failures of the typical development process like a. chaos due to changing requirements, unrealistic estimates of time, cost and quality of the product. Meetings 1.      Daily Scrum meeting or daily stand up meeting: agenda:  what is done, what is planned for today, what are the problems in accomplishing the goal? 2.      Sprint planning meeting : Before each sprint cycle (7-30 days)starts, prepare sprint backlog, timelines, 3.      Sprint review meeting: done at the end of sprint cycle, review work completed and not completed, demo the work completed, do not demo incomplete work, 4 hour time will be allocated. 4.      Sprint retrospective meeting: done at the end o
Read More