Skip to main content

Google Calendar - High Level Design of tests

Last month I had the chance to work on a set of High level test design documents for the Google Calendar web application.

Click here to refer to the set of documents for reference.

Please note that:
1. Bullet marks are not accurately reflected in uploaded word documents.
2. UI specific Images have been posted in automation scenario document only for ease of reference, in usual cases one should refrain from doing this in a running test automation project, because UI can undergo changes!
Labels:
Location: Pune, Maharashtra, India

Comments

Post a Comment

Popular posts from this blog

Multi XSD XML Validation

  This program validates XMLs against referenced XSDs. The XSDs are assumed to be external to (not embedded in) the XML. List the XSDs and XMLs details in separate sheets in the program’s excel book and run the program. The program will generate errors/ warnings in console window.
Post a Comment
Read more

Two-way XML Diffgram (XML structure sensitive)

     With pretty printed source XMLs: Same source XMLs, but in single line – diffgram output remains the same: Download the program files from here .
Post a Comment
Read more

Study of an AngularJS application: Feeding Excel based data into an SVG Flowchart with AngularJS and NodeJS

Reference article Implementing a Flowchart with SVG and AngularJS Source code from original article is here .   Customization goals a) Feed the SVG flowchart nodes from excel datasheet b) Understand a bit of the AngularJS and NodeJS client-server communication c) Learn javascript debugging on server side as well as client side using VS Code editor As a beginner to AngularJS-NodeJS, the customization is based on a partial study of the original article .   Most challenging challenge as a dummy There was a space of time when I thought I was publishing the server side JSON data to the same URL as the front-end html page. And then trying to debug it and not knowing why: in one case the data was coming from the server side only, while in the other case it was coming from mocked data on client side. Kept on looking for whether data was getting lost, or did I need routing. There were debug sessions where both server side and client side individually appear...
1 comment
Read more