DOCSLIB.ORG

Rapise V2.0 User Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Rapise V2.0 User Guide About this Guide Top Previous Next The Rapise User's Guide is divided into four sections: Getting Started; Features; Dialogs, Views, and Menus; HowTos. Getting Started The Getting Started section is for new Rapise users. It has the following subsections: (1) An Overview of Rapise: what it's for and how to use it. (2) Test Samples, where the sample projects included with Rapise are described. (3) TwoDialogs Sample, a step-by-step tutorial for creating your first test with Rapise (4) Tutorial: Record and Playback, a slightly more advanced tutorial in using Rapise to test a web page. (5) Tutorial: Testing REST Web Services, a tutorial in using Rapise to test a RESTful web service API. Features The features of Rapise are many. Features have been designed to make all aspects of test automation as easy as possible. Most of the features of Rapise fall into one of five categories: (1) Building test scripts with little or no manual scripting. (2) Reading and interpreting results and reports. (3) Additional features and capabilities for sophisticated testing. (4) Writing more involved or complicated tests using scripting. (5) Extending Rapise to learn new or extended libraries of capabilities. Depending on the application set being tested, not all of these features are necessarily needed for every situation. For each feature, this document attempts to present: (1) The reason you might use a given feature. (2) A summary of the basic value of the feature. (3) An overview of how the feature works from the perspective of using it. (4) At least one useful sample that demonstrates how to use the feature. Dialogs, Views, and Menus This section details the Rapise GUI. Each subsection describes the function of a particular Dialog, View, or Menu. The purpose and consequences of all buttons, options, lists, and check boxes are listed. HowTos This section focuses on specific tasks that a Rapise user might want to accomplish. Glossary Top Previous Next This glossary presents a list of terms and their definitions as they are used in this guide. API - Application Programming Interface AUT - Application Under Test DOM - Document Object Model GUI - Graphical User Interface GWT - Google Web Toolkit IDE - Integrated Development Environment JSON - JavaScript Object Notation REST - REpresentation State Transfer SOAP - Simple Object Access Protocol UI - User Interface XML - eXtensible Markup Language YUI - Yahoo! User Interface (library) Getting Started Top Previous Next The Getting Started section is for new Rapise users. It has the following subsections: (1) An Overview of Rapise: what it's for and how to use it. (2) Test Samples, where the sample projects included with Rapise are described. (3) TwoDialogs Sample, a step-by-step tutorial for creating your first test with Rapise (4) Tutorial: Record and Playback, a slightly more advanced tutorial in using Rapise to test a web page. (5) Tutorial: Testing Adobe Flex Applications, a slightly more advanced tutorial in using Rapise to test an Adobe Flex/Flash/AIR application. (6) Tutorial: Testing REST Web Services, a tutorial in using Rapise to test a RESTful web service API. Overview Top Previous Next Rapise was created to make software testing easy and manageable without being prohibitively expensive. Rapise was made easy for software test professionals, developers and professionals concerned with quality assurance to simply and quickly write a test to cover an application, a web page, or a single bug to prevent regression. Consider for a moment what it is you do to test your software today. Most likely it has some for of user interface (UI), probably a graphic user interface (GUI). So you will run the application , click around, perhaps in some way that gives you complete coverage of all the features (but probably not if it's a large application or web). Then you will login, if appropriate, and you will fetch some data and modify some data, test some more controls - edit boxes, buttons, drop-down lists, links, etc. If you have just fixed a bug then you will focus on the area of the application where the bug occurred. You will enter data that causes the bug, or go through the control sequence that causes the bug. 5/15/2014 Page 1 of 97 Next time you come to fix a bug in this application, you will do the same thing again.. Once again, you will focus on the area where the bug was. Rapise presents you with two methods for capturing specific tests, and it will keep the test as a solo test or as part of a suite of tests that help you to qualify the application for release or a more formal QA process. Rapise is designed to allow the developer or the test professional to add new tests quickly and so to build up a library of tests. There are two methods for capturing tests: x Record and playback. In this type of test creation, you turn on the recorder and perform the actions needed to execute the test. Each test is saved to its own directory. A test consists of a javascript test script (.js), a meta-data file (*.sstest), and any number of additional supplementary scripts and data files. The test script is automatically generated after recording; simple modifications are required to make the test data driven. Checkpoints can be added during recording, or manually into the script. x Object-driven learning. Rapise considers each item on the page or within the application window to be an object. Examples are buttons, edit boxes, links, etc. To create a test using this technique, you have Rapise "learn" each control, and it will keep a miniature database of all the controls you "teach" it. To create a test, you write a script to instruct Rapise to perform a particular action on each object in the prescribed order. As any point along the way, the script you write can instruct Rapise to look inside an object and read its data and compare that value or content with what you expect it o be. There are many methodologies with their own recommended approaches for designing testing strategies to ensure that application coverage is complete and meets the business requirements specification of the work being accomplished. Inflectra in general, recommends that you create a new test for each software requirement (to track progress) and for each issue in your issue tracking system (to test for regressions). To help you manage the requirements and issue tracking processes and to ensure that you have adequate test coverage, Inflectra recommend that you use Rapise with a test management system such as SpiraTest. That way you can maintain all your requirements, test cases and defects in a single place. Once you have created the test, you can playback your test from within Rapise, run it from the command-line or execute it remotely using RapiseLauncher in conjunction with SpiraTest. A report detailing the outcome of each step of the test will be automatically generated. Recording, playback, the report, and the Rapise engine are all customizable. Samples Index Top Previous Next Rapise includes several sample tests that you are free to read, modify, copy and use. They are located in: RapiseDataDirectory\Samples. Unless you specified otherwise, the RapiseDataDirectory will be: C:\Users\Public\Documents\Rapise. The sample tests are described below. ActiveX These samples demonstrate the testing of Microsoft ActiveX / COM controls used in Visual Basic applications including the MSComCtl library. The samples include the Microsoft FlexGrid Control, MS Common Toolbar Control, Microsoft Tabbed Dialog Control, TabStrip, and Microsoft Windows Common Controls 6.0 [MSCOMCTL.OCX]. AdobeFlex3 This is a set of regression tests for Adobe Flex 3.x controls. AdobeFlex4 This is a set of regression tests for Adobe Flex 4.x controls. AnalogRecorder This sample demonstrates Analog Recording. CrossBrowser A simple recorded test is modified to run on both Firefox and Internet Explorer. Read the Cross Browser Testing HowTo for more details. DotNet20 This sample tests a .NET 2.0 application. This sample demonstrates the capabilities of the .NET library. The application under test contains various standard GUI controls, such as: button, edit, tree, combo box, menu, etc. FarPoint This sample script demonstrates using the FarPoint library to test the FarPoint SpreadSheet Control. Java This sample tests a Java AWT/SWING application. This sample demonstrates the capabilities of the Java library. The application under test contains various standard GUI controls, such as: button, edit, tree, combo box, menu, etc. Java SWT This sample tests a Java SWT/RCP application. This sample demonstrates the capabilities of the SWT and UIAutomation libraries. The application under test contains various standard GUI controls, such as: button, edit, tree, combo box, menu, etc. jQuery-UI This sample illustrates using the jQuery HTML DOM extension library that allows you to record/playback test scripts against web applications using widgets from the jQuery Javascript library framework. Library Information System These tests can be used to test the sample library information system web application hosted at http://www.libraryinformationsystem.net. This is the same sample application used by SpiraTest and illustrates how you can use SpiraTest to manage and execute automated Rapise tests. A copy of these tests is also available in new installations of SpiraTest v3.2+. Managed This sample tests a .NET 2.0 application. This sample demonstrates the capabilities of the Managed library. The application under test contains various standard GUI controls, such as: button, edit, tree, combo box, grid, listbox, listview, menu, etc. QtFramework TThis sample tests a sample QT Framework cross-platform application. This sample demonstrates the capabilities of the QtFramework library. The application under test contains various standard Qt widgets, such as: button, edit, tree, combo box, etc.
Load more

Recommended publications
  • Pragmatic Guide to Javascript
    www.allitebooks.com What Readers Are Saying About Pragmatic Guide to J a v a S c r i p t I wish I had o w n e d this book when I first started out doing JavaScript! Prag- matic Guide to J a v a S c r i p t will take you a big step ahead in programming real-world JavaScript by showing you what is going on behind the scenes in popular JavaScript libraries and giving you no-nonsense advice and back- ground information on how to do the right thing. W i t h the condensed years of e x p e r i e n c e of one of the best JavaScript developers around, it’s a must- read with great reference to e v e r y d a y JavaScript tasks. Thomas Fuchs Creator of the script.aculo.us framework An impressive collection of v e r y practical tips and tricks for getting the most out of JavaScript in today’s browsers, with topics ranging from fundamen- tals such as form v a l i d a t i o n and JSON handling to application e x a m p l e s such as mashups and geolocation. I highly recommend this book for anyone wanting to be more productive with JavaScript in their web applications. Dylan Schiemann CEO at SitePen, cofounder of the Dojo T o o l k i t There are a number of JavaScript books on the market today, b u t most of them tend to focus on the new or inexperienced JavaScript programmer.
    [Show full text]
  • THE FUTURE of SCREENS from James Stanton a Little Bit About Me
    THE FUTURE OF SCREENS From james stanton A little bit about me. Hi I am James (Mckenzie) Stanton Thinker / Designer / Engineer / Director / Executive / Artist / Human / Practitioner / Gardner / Builder / and much more... Born in Essex, United Kingdom and survived a few hair raising moments and learnt digital from the ground up. Ok enough of the pleasantries I have been working in the design field since 1999 from the Falmouth School of Art and onwards to the RCA, and many companies. Ok. less about me and more about what I have seen… Today we are going to cover - SCREENS CONCEPTS - DIGITAL TRANSFORMATION - WHY ASSETS LIBRARIES - CODE LIBRARIES - COST EFFECTIVE SOLUTION FOR IMPLEMENTATION I know, I know, I know. That's all good and well, but what does this all mean to a company like mine? We are about to see a massive change in consumer behavior so let's get ready. DIGITAL TRANSFORMATION AS A USP Getting this correct will change your company forever. DIGITAL TRANSFORMATION USP-01 Digital transformation (DT) – the use of technology to radically improve performance or reach of enterprises – is becoming a hot topic for companies across the globe. VERY DIGITAL CHANGING NOT VERY DIGITAL DIGITAL TRANSFORMATION USP-02 Companies face common pressures from customers, employees and competitors to begin or speed up their digital transformation. However they are transforming at different paces with different results. VERY DIGITAL CHANGING NOT VERY DIGITAL DIGITAL TRANSFORMATION USP-03 Successful digital transformation comes not from implementing new technologies but from transforming your organisation to take advantage of the possibilities that new technologies provide.
    [Show full text]
  • Wireless Assistive Head Controlled Mouse with Eye-Blink Detection for Enhanced Actions
    Turkish Journal of Physiotherapy and Rehabilitation; 32(2) ISSN 2651-4451 | e-ISSN 2651-446X WIRELESS ASSISTIVE HEAD CONTROLLED MOUSE WITH EYE-BLINK DETECTION FOR ENHANCED ACTIONS ALAN FRANCIS CHEERAMVELIL1, ARJUN ALOSHIOUS2, N. DHARANIDEVI3, S. VARUN4, ABEY ABRAHAM5 5Assistant Professor, Department of Information Technology, Rajagiri School of Engineering & Technology, Kerala, India- 682039 1,2,3,4Student, Department of Information Technology, Rajagiri School of Engineering & Technology, Kerala, India-682039 [email protected], [email protected], [email protected], [email protected], [email protected] ABSTRACT The Wireless Assistive Head Controlled Mouse with Eye-Blink Detection for enhanced actions is an assistive Human Interface Device aimed at quadriplegic people. The current pandemic has made the world more reliant on digital means of communications than ever before and people with motor disability have no means to access these resources. A majority of them have good head movement but no torso movement. The proposed device uses a Gyroscope sensor to accurately map the user’s head movements to the corresponding mouse coordinates. The device works with Bluetooth Low Energy technology enabling the user to control the digital devices at a comfortable range without the hassle of wires. The plug-N-play feature allows the use of the device without additional drivers. For more sophisticated usage scenarios, the user can choose between the various traditional mouse operations using a desktop software with the help of the eye-blink detection using image processing. Keywords— Assistive technologies; Persons with disability; Gyroscope sensor; Human Computer Interaction; Eye-blink Detection; I. INTRODUCTION According to the Census conducted in 2011, persons with disability (PwD) constitute 2.21% of the total population in India.
    [Show full text]
  • User Manual Introduction
    Item No. 8015 User Manual Introduction Congratulations on choosing the Robosapien Blue™, a sophisticated fusion of technology and personality. With a full range of dynamic motion, interactive sensors and a unique personality, Robosapien Blue™ is more than a mechanical companion; he’s a multi-functional, thinking, feeling robot with attitude! Explore Robosapien Blue™ ’s vast array of functions and programs. Mold his behavior any way you like. Be sure to read this manual carefully for a complete understanding of the many features of your new robot buddy. Product Contents: Robosapien Blue™ x1 Infra-red Remote Controller x1 Pick Up Accessory x1 THUMP SWEEP SWEEP THUMP TALK BACKPICK UP LEAN PICK UP HIGH 5 STRIKE 1 STRIKE 1 LEAN THROW WHISTLE THROW BURP SLEEP LISTEN STRIKE 2 STRIKE 2 B U LL P D E O T Z S E R R E S E T P TU E R T N S S N T R E U P T STRIKE 3 R E S E R T A O R STRIKE 3 B A C K S S P T O E O P SELECT RIGHT T LEF SONIC DANCE D EM 2 EXECUTE O O 1 DEM EXECUTE ALL DEMO WAKE UP POWER OFF Robosapien Blue™ Remote Pick Up Controller Accessory For more information visit: www.wowwee.com P. 1 Content Introduction & Contents P.1-2 Battery Details P.3 Robosapien Blue™ Overview P.4 Robosapien Blue™ Operation Overview P.5 Controller Index P.6 RED Commands - Upper Controller P.7 RED Commands - Middle & Lower Controller P.8 GREEN Commands - Upper Controller P.9 GREEN Commands - Middle & Lower Controller P.10 ORANGE Commands - Upper Controller P.11 ORANGE Commands - Middle & Lower Controller P.12 Programming Mode - Touch Sensors P.13 Programming Mode - Sonic Sensor P.14 Programming Mode - Master Command P.15 Troubleshooting Guide P.16 Warranty P.17 App Functionality P.19 P.
    [Show full text]
  • Overview Work Experience Skills Contact Education
    OVERVIEW Have over 6 years experience in development E-Learning Tool, 1 year experience in development Search Engine website; 1 year in defect tracking tool, 6 months experience in development Task Management tool; 4 years experience in development Enterprise Social Network. Skill in C/C++, VC++, Java Springframework, C#, ASP.Net, Linq, WPF, WCF, JavaScript., .Net Framework 1.x, Net Framework 2.0, 3.5, 4.0, REST API. Good knowledge in Object Oriented Programming. Have years experience in C++, VC++, C#.Net, Java, Javascript and 6 years experience in Cross Platforms Programming, System Events Hook technique, Application Programming Interface Hook technique, Java Access Bridge, Microsoft Active Accessibility, and IHTML, Java, Spring MVC. CONTACT WORK EXPERIENCE 03 Apr, 1981 Senior Software Engineer January, 2014- Now Ho Chi Minh City PROJECT: ZILLABLE Project Description: Enterprise Social Network EDUCATION Industry: Social Network Project Team Size: 15+ Bachelor – Information Technology, Role(s): Developer, Component owner University of Sciences and Natural, Skill Set Utilized: Ho Chi Minh City, VietNam Languages: Java, AngularJS Middleware: MongoDB, Elasticsearch SKILLS Others: REST API, Integration: Google APIs, OneDrive API, DropBox, Interested in and researching: Box Auth2 AI Responsibilities: Programming Crypto, Smart Contract Number of People Managed: 0 FinTech Assignment Duration Algorithms High level programming: Senior Software Engineer January, 2013 - 2014 define data models and basic PROJECT: INTEGRIS relationships for code generation
    [Show full text]
  • Learning Javascript Design Patterns
    Learning JavaScript Design Patterns Addy Osmani Beijing • Cambridge • Farnham • Köln • Sebastopol • Tokyo Learning JavaScript Design Patterns by Addy Osmani Copyright © 2012 Addy Osmani. All rights reserved. Revision History for the : 2012-05-01 Early release revision 1 See http://oreilly.com/catalog/errata.csp?isbn=9781449331818 for release details. ISBN: 978-1-449-33181-8 1335906805 Table of Contents Preface ..................................................................... ix 1. Introduction ........................................................... 1 2. What is a Pattern? ...................................................... 3 We already use patterns everyday 4 3. 'Pattern'-ity Testing, Proto-Patterns & The Rule Of Three ...................... 7 4. The Structure Of A Design Pattern ......................................... 9 5. Writing Design Patterns ................................................. 11 6. Anti-Patterns ......................................................... 13 7. Categories Of Design Pattern ............................................ 15 Creational Design Patterns 15 Structural Design Patterns 16 Behavioral Design Patterns 16 8. Design Pattern Categorization ........................................... 17 A brief note on classes 17 9. JavaScript Design Patterns .............................................. 21 The Creational Pattern 22 The Constructor Pattern 23 Basic Constructors 23 Constructors With Prototypes 24 The Singleton Pattern 24 The Module Pattern 27 iii Modules 27 Object Literals 27 The Module Pattern
    [Show full text]
  • Slow Blink Eye Closure in Shelter Cats Is Related to Quicker Adoption
    animals Article Slow Blink Eye Closure in Shelter Cats Is Related to Quicker Adoption Tasmin Humphrey 1,* , Faye Stringer 1, Leanne Proops 2 and Karen McComb 1,* 1 Mammal Communication and Cognition Research Group, School of Psychology, University of Sussex, Brighton BN1 9QH, UK; [email protected] 2 Centre for Comparative and Evolutionary Psychology, Department of Psychology, University of Portsmouth, Portsmouth PO1 2DY, UK; [email protected] * Correspondence: [email protected] (T.H.); [email protected] (K.M.) Received: 27 October 2020; Accepted: 23 November 2020; Published: 30 November 2020 Simple Summary: Slow blinking is a type of interaction between humans and cats that involves a sequence of prolonged eye narrowing movements being given by both parties. This interspecific social behaviour has recently been studied empirically and appears to be a form of positive communication for cats, who are more likely to approach a previously unfamiliar human after such interactions. We investigated whether slow blinking can also affect human preferences for cats in a shelter environment. We measured whether cats’ readiness to respond to a human-initiated slow blink interaction was associated with rates of rehoming in the shelter. We also examined cats’ propensity to slow blink when they were anxious around humans or not. We demonstrated that cats that responded to human slow blinking by using eye closures themselves were rehomed quicker than cats that closed their eyes less. Cats that were initially identified as more nervous around humans also showed a trend towards giving longer total slow blink movements in response to human slow blinking.
    [Show full text]
  • The Effect of Ajax on Performance and Usability in Web Environments
    The effect of Ajax on performance and usability in web environments Y.D.C.N. op ’t Roodt, BICT Date of acceptance: August 31st, 2006 One Year Master Course Software Engineering Thesis Supervisor: Dr. Jurgen Vinju Internship Supervisor: Ir. Koen Kam Company or Institute: Hyves (Startphone Limited) Availability: public domain Universiteit van Amsterdam, Hogeschool van Amsterdam, Vrije Universiteit 2 This page intentionally left blank 3 Table of contents 1 Foreword ................................................................................................... 6 2 Motivation ................................................................................................. 7 2.1 Tasks and sources................................................................................ 7 2.2 Research question ............................................................................... 9 3 Research method ..................................................................................... 10 3.1 On implementation........................................................................... 11 4 Background and context of Ajax .............................................................. 12 4.1 Background....................................................................................... 12 4.2 Rich Internet Applications ................................................................ 12 4.3 JavaScript.......................................................................................... 13 4.4 The XMLHttpRequest object..........................................................
    [Show full text]
  • Meeting Minutes Template Google Docs
    Meeting Minutes Template Google Docs Emerson narrows uncouthly as unleaded Rhett Photostats her weeds hex virulently. Clifton parts yore. Unblemished Virgil delates that lucidness entwining offensively and infests elementally. Once you could prove harmful to give a daily standups would any meeting minutes templates, may or question in your The templates include predesigned sections where did record meeting details. This is a more efficiency, google docs word or confirmation email address to read. Ability to be saved as well as view only with google. Below are outdated example templates as complete as tips and ideas to job you get started with maritime and preparing effective meeting minutes What are meeting. Download Word docx For Word 2007 or later Google Docs Description Free Writing Meeting Minutes Template October 23 20xx Plus it adds a tomb of. Enter the time that want to master templates offers a lot of the approaches that it helps you need to create a text. Blog post drafts company documentation meeting notes or even whitepapers. PandaDoc Track eSign Sales Docs Get surveillance on Google Play. Can use google docs templates you for the necessary details of minutes meeting template google docs. Slides can help you format it offers a regular basis and even easier access meeting notes, other common that holds several benefits of this attendance. Add special purpose of the staff or associated with your document also slow your content in a printable pdf a structured and you can. What a google docs to and quick agenda will find it can get an assistant to enter the user interface, not need to go.
    [Show full text]
  • The Chrome Process
    The Chrome Process Matt Spencer UI & Browser Marketing Manager 1 Overview - Blink . Blink is a web engine . Others include WebKit, Gecko, Trident, … . It powers many browsers . Chrome, Opera, … . It is Open Source . Open governance <blink> . Open discussion . Open development . HTML spec is implemented in Blink 6 Why should you be involved? Web Facing improvements Internal Architectural improvements . HTML features that drive core business . Improvements that target your SoC . WebVR . Impact battery life . Telepresence . Enhance user experience . … . You can influence the platform . Help create a better embedded web story 7 The Blink Intent Process - Enhancement http://www.chromium.org/blink#launch-process Intent to Implement Intent to Ship . Email sent to blink-dev mailing list . Email sent to blink-dev mailing list . A template for the email is provided . A template for the email is provided . Announces intent to community . Allows discussion about implementation . Allows early discussion . Requires spec (w3c, whatwg,…) published . Requires info on intent from other vendors . No formal authorization required . Formal authorization required . Implementation off-tree . Need approval from 3 API owners . No commits back to blink repos LGTM (looks good to me) sent to blink-dev 8 The Blink Intent Process - Deprecation http://www.chromium.org/blink#launch-process Intent to Deprecate Intent to Remove . Email sent to blink-dev mailing list . Email sent to blink-dev mailing list . A template for the email is provided . A template for the email is provided . If a web facing feature (css, html, js) . Formal approval required . Measure usage of the feature . Wait for 3 LGTMs from API owners . Add usage counter to blink .
    [Show full text]
  • Database Client Installation Guide
    Oracle® Database Database Client Installation Guide 18c for HP-UX Itanium E83741-01 November 2018 Oracle Database Database Client Installation Guide, 18c for HP-UX Itanium E83741-01 Copyright © 2015, 2018, Oracle and/or its affiliates. All rights reserved. Primary Author: Prakash Jashnani Contributing Authors: Douglas Williams Contributors: Mark Bauer, David Austin, Neha Avasthy, Prasad Bagal, Subhranshu Banerjee, Mark Bauer, Tammy Bednar, Eric Belden, Gavin Bowe, Robert Chang, Darcy Christensen, Kiran Chamala, Jonathan Creighton, Benoit Dageville, Sudip Datta, Jim Erickson, Marcus Fallen, Joseph Francis, Mark Fuller, Allan Graves, Barbara Glover, Asad Hasan, Thirumaleshwara Hasandka, Prasad Kuruvadi Nagaraj, Clara Jaeckel, Aneesh Khandelwal, Joel Kallman, Eugene Karichkin, Jai Krishnani, Sangeeth Kumar, Ranjith Kundapur, Kevin Jernigan, Christopher Jones, Simon Law, Bryn Llewellyn, Saar Maoz, Sreejith Minnanghat, Gopal Mulagund, Sue Lee, Rich Long, Barb Lundhild, Rolly Lv, Rudregowda Mallegowda, Padmanabhan Manavazhi, Mughees Minhas, Krishna Mohan, Matthew McKerley, John McHugh, Gurudas Pai, Satish Panchumarthy , Rajesh Prasad, Rajendra Pingte, Apparsamy Perumal, Srinivas Poovala, Mohammed Shahnawaz Quadri, Hanlin Qian, Gurumurthy Ramamurthy, Hema Ramamurthy, Sunil Ravindrachar, Mark Richwine, Dipak Saggi, Trivikrama Samudrala, Shachi Sanklecha, David Schreiner, Ara Shakian, Mohit Singhal, Dharma Sirnapalli, Akshay Shah, James Spiller, Roy Swonger, Binoy Sukumaran, Kamal Tbeileh, Ravi Thammaiah, Shekhar Vaggu, Parvathi Subramanian, Ajesh Viswambharan, Peter Wahl, Terri Winters, Sergiusz Wolicki, Sivakumar Yarlagadda, Zakia Zerhouni This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.
    [Show full text]
  • Roboto Installation Instructions
    Roboto Installation Instructions works with the Google Assistant Please read and save these instructions before installation DO NOT RETURN TO STORE 2 Roboto Instructions FR-W1910 General Inquiries For all questions about your ceiling fan please read all included instructions, installation procedures, troubleshooting guidelines and warranty information before starting installation. For missing parts or general inquiries call our trained technical staff at: 1-866-810-6615 option 0 MON-FRI 8AM-8PM EST Email: [email protected] Or live chat at modernforms.com Fan Support For fast service have the following information below when you call: 1. Model Name and Number 2. Part Number and Part Description 3. Date Of Purchase and Purchase Location 1-866-810-6615 option 1 MON-FRI 8AM-8PM EST Email: [email protected] FR-W1910 Roboto Instructions 3 Safety Rules For operation, maintenance, and troubleshooting information, visit http://modernforms.com/fan-support/ To reduce the risk of electric shock, ensure electricity has been turned off at the circuit breaker before beginning. All wiring must be in accordance with the National Electrical Code “ANSI/NFPA 70” and local electrical codes. Electrical installation should be performed by a licensed electrician. The fan must be mounted with a minimum of 7 ft. (2.1m) clearance from the trailing edge of the fan blades to the floor and a minimum of 1.5 ft (0.5m) from the edge of the fan blades to the surrounding walls. Never place objects in the path of the fan blades. To avoid personal injury or damage to the fan and other items, please be cautious when working around or cleaning the fan.
    [Show full text]