DOCSLIB.ORG

QA Wizard Pro User Guide V2017.1

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
QA Wizard Pro User Guide V2017.1 QA Wizard Pro User Guide Version 2017.1 Copyrights © 1996-2017 Perforce Software, Inc. and its subsidiaries. All rights reserved. Defect Scribe, Helix ALM, Helix ALM Suite, Helix Issue Management, Helix Requirements Management, Helix Test Case Management, QA Wizard Pro, Resource Thief, SoloBug, SoloSubmit, Surround SCM, and TestTrack are trademarks or registered trademarks of Perforce Software, Inc. and its subsidiaries in the United States and other countries. Acrobat Reader is a registered trademark of Adobe, Inc. in the United States and other countries. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited. Apple, Mac, Mac OS, macOS, Macintosh, Objective-C, and Safari are registered trademarks of Apple Computer, Inc. Chrome is a registered trademark of Google Inc. Debian is a registered trademark of Software in the Public Interest, Inc. Firefox is a registered trademark of the Mozilla Foundation. Linux is a trademark of Linus Torvalds. Microsoft, Windows, Windows Server, Windows Vista, MS Windows, Active Directory, Internet Explorer, Outlook, SQL Server, Visual SourceSafe, and Visual Studio are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. openSUSE and SUSE are registered trademarks of Novell Inc. in the United States and other countries. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Red Hat, Red Hat Enterprise Linux, and Fedora are registered trademarks of Red Hat, Inc. in the United States and other countries. Ubuntu is a registered trademark of Canonical Ltd. All other product names mentioned herein are the trademarks of their respective owners. All other trademarks are the property of their respective owners. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language in any form by any means without the written permission of Perforce Software, Inc. and its subsidiaries. Your license agreement with Perforce Software, Inc. or any of its subsidiaries, which is included with the product, specifies the permitted and prohibited uses of the product. Any unauthorized duplication or use of this software, in whole or in part, in print, or in any other storage and retrieval system is forbidden. Information in this document is subject to change without notice and does not represent a commitment on the part of Perforce Software, Inc. or any of its subsidiaries. Unless otherwise noted, all companies, products, street addresses, and persons contained herein are purely fictitious. Mention of third-party companies and products is for informational purposes only and does not constitute an endorsement. Perforce Software, Inc. and its subsidiaries 400 N 1st Avenue Suite 200 Minneapolis, Minnesota 55401 USA +1 510.864.7400 [email protected] Contents What's New 1 Installing QA Wizard Pro 3 Before you install 3 Running the installer 4 After installation 6 Getting Started with QA Wizard Pro 7 Key QA Wizard Pro concepts 8 Understanding the testing process 9 Starting QA Wizard Pro 11 Managing licenses 11 QA Wizard Pro interface 11 Application Repository pane 13 Call Stack pane 14 Errors pane 15 Find Results pane 15 Output pane 15 Pending Changes pane 16 Preview pane 16 References pane 17 Reports pane 17 Script pane 18 Statements pane 19 Helix ALM panes 20 Variables pane 20 Workspace pane 21 Sample scripts and applications 22 Creating workspaces 23 Adding existing files to workspaces 23 Using folders 24 Modifying workspace properties 25 Opening workspaces 26 Using Keyword View 27 Using Text View 28 Declaring variables in Text View 29 Declaring arrays in Text View 31 i Creating functions and subroutines in Text View 32 Setting Text View font and color options 34 Customizing QA Wizard Pro 35 Customizing the interface 35 Customizing toolbars 36 Creating toolbars 37 Adding toolbar and menu commands 37 Modifying toolbar and menu commands 38 Setting toolbar and menu options 38 Customizing keyboard shortcuts 39 Setting general options 40 Setting server connection options 43 Setting email notification options 44 Managing Applications 47 Adding applications 47 Copying applications 49 Exporting applications 49 Importing applications 50 Promoting applications 50 Modifying application properties 51 Adding versions 51 Modifying version properties 53 Deleting versions 54 Deleting applications 54 Managing Application Repositories 57 About application repositories 57 Setting up repositories 59 Maintaining repositories 60 Populating repositories 60 Overriding global application startup information 62 Connecting to the global repository 63 Recording Scripts 65 Recording new scripts 65 Selecting the default web browser 68 Recording additional script steps 69 ii Recording low-level actions 70 Adding new scripts 71 Understanding recorded scripts 71 Running Scripts to Perform Tests 73 Running scripts 73 Setting and running a main script 74 Entering login information when running scripts 74 Viewing results reports 75 Exporting results reports 76 Setting playback options 76 Setting reporting options 78 Running multiple scripts 79 Running scripts against a global repository 79 Running scripts from a command prompt 80 Creating batch files 83 Modifying batch files 86 Running batch files 87 Monitoring Script Playback 89 Viewing playback information in the dashboard 90 Dashboard widget types 92 Changing information displayed in dashboard widgets 95 Installing and configuring the dashboard 97 Viewing playback information in the status tool 99 Load Testing 103 Recording load test scripts 103 Running load tests 104 Running load tests from a command prompt 106 Viewing load test results reports 109 Stress Testing 111 Creating and running stress tests 111 Applying stresses 112 Managing Windows and Controls 115 Capturing window and control data 115 Reviewing and saving repository changes 116 Repository change reasons 118 iii About smart matching 118 Overriding naming conventions for new controls 119 Default control naming convention 121 Modifying window and control properties 122 About search methods 124 Changing standard search criteria 124 Editing window and control properties 126 Using regular expressions 127 Changing the search method for multiple controls 128 Using the Function search method 129 Setting advanced control properties 131 Changing control types 132 Renaming windows and controls 133 Finding and replacing property values 134 Merging controls 136 Configuring user-added windows and controls 136 Manually adding windows and controls to application repositories 138 Adding properties to user-added windows and controls 140 Deleting properties from user-added windows and controls 142 Duplicating windows and controls 142 Editing and deleting user-added windows and controls 143 Synchronizing with the application repository 143 Synchronizing multiple scripts with the application repository 144 Testing context menus 144 Modifying Scripts 145 Adding statements 146 Statement value types 147 Using function results as statement arguments 148 Adding browser actions 149 Cleaning up scripts 150 Editing statements 151 Deleting statements 151 Calling scripts from other scripts 151 Finding variable, function, and subroutine references in scripts 153 Finding variable, function, and subroutine definitions in scripts 153 iv Commenting blocks of steps 154 Handling known exceptions 155 Handling script errors 155 Identifying files and directories in statements 156 Finding and replacing text in scripts 157 Finding and replacing text in individual scripts 158 Finding text in multiple scripts 159 Replacing text in multiple scripts 160 Encrypting text 162 Working with text in HTML elements 162 Modifying script properties 163 About drag-and-drop scripting 164 Using Checkpoints 165 Checkpoint types 165 Creating record-time checkpoints 166 Creating record-time check exists checkpoints 168 Creating checkpoints 169 Editing checkpoints 171 Creating exists checkpoints 171 Creating image checkpoints 173 Editing image checkpoints 175 Creating expression checkpoints 176 Creating string exists checkpoints 177 Deleting checkpoints 177 Checkpoint examples 178 Capturing and checking property values during playback 179 Using OCR to Work with Graphical Text 181 Creating OCR checkpoints 183 Troubleshooting OCR issues 186 Creating Data-Driven Scripts 187 About datasheets 187 Creating local datasheets 187 Adding existing local datasheets 188 Importing external test data 189 Linking to external test data 189 v Configuring external datasheets 190 Creating Microsoft Access datasheets 190 Creating Microsoft Excel datasheets 192 Creating Microsoft SQL Server datasheets 193 Creating Oracle datasheets 195 Creating PostgreSQL datasheets 197 Creating SQLite datasheets 199 Creating text file datasheets 200 Associating datasheets with scripts 203 Using datasheet values in scripts 203 Navigating datasheets 205 Retrieving external data with database queries 206 Retrieving external data with script-generated queries 207 Editing local datasheets 208 Modifying local datasheet properties 208 Deleting local datasheets 209 Modifying external datasheet properties 209 Deleting external datasheets 210 Debugging Scripts 211 Running scripts in debug mode 211 Using breakpoints 212 Using the INDEBUGMODE variable 213 Troubleshooting variables 213 Using Repository Variables 215 Creating repository variables 215 Editing repository variables 217 Deleting repository variables 217 Managing repository
Load more

Recommended publications
  • Useful Tools for Game Making
    CMS.611J/6.073 Fall 2014 Useful Tools List This list is by no means complete, but should get you started. Talk to other folks in the class about their recommendations. Revision Control Version control software, provides backups and easy reversion. Perforce Mac/Win GUI (p4v): Heavily used in game http://www.perforce.com/dow industry. Commercial nloads/Perforce-Software-Ver software; you can use the sion-Management/complete_l Game Lab server. ist/Customer Subversion Command line: Open source, server-based http://subversion.apache.org/ Windows GUI: http://tortoisesvn.net/ Git Command line: Open source, distributed http://git-scm.com/ Mercurial Command line: Open source, distributed http://mercurial.selenic.com/ Windows GUI: http://tortoisehg.bitbucket.org/ SourceTree Mac/Win GUI: Not a source control system, http://www.sourcetreeapp.co just a GUI for Git and m/ Mercurial clients Revision Control Hosting SourceForge http://sourceforge.net/ git, mercurial, or subversion BitBucket https://bitbucket.org/ git or mercurial GitHub https://github.com/ git, has own (painful) GUI for Git 1 Image Editing MSPaint Windows, pre-installed Surprisingly useful quick pixel art editor (esp for prototypes) Paint.NET Windows, About as easy as MSPaint, but http://www.getpaint.net/download much more powerful .html Photoshop Mac, Windows New Media Center, 26-139 GIMP Many platforms, Easier than photoshop, at http://www.gimp.org/downloads/ least. Sound GarageBand Mac New Media Center, 26-139 Audacity Many platforms, Free, open source. http://audacity.sourceforge.ne
    [Show full text]
  • Seapine ALM Reporting Platform Database Reference Guide V2016.1
    Seapine ALM Data Warehouse Database Reference Guide Version 2016.1 Contents Key entities ................................................................................................................................................................... 1 Repository ................................................................................................................................................................. 1 License Server .......................................................................................................................................................... 1 QA Wizard Pro .......................................................................................................................................................... 1 Surround SCM ........................................................................................................................................................... 1 TestTrack ................................................................................................................................................................... 2 Data dictionary ............................................................................................................................................................. 5 Table: LS_AUTHENTICATION_METHOD ................................................................................................................ 5 Table: LS_EMAIL .....................................................................................................................................................
    [Show full text]
  • Jenkins Job Builder Documentation Release 3.10.0
    Jenkins Job Builder Documentation Release 3.10.0 Jenkins Job Builder Maintainers Aug 23, 2021 Contents 1 README 1 1.1 Developers................................................1 1.2 Writing a patch..............................................2 1.3 Unit Tests.................................................2 1.4 Installing without setup.py........................................2 2 Contents 5 2.1 Quick Start Guide............................................5 2.1.1 Use Case 1: Test a job definition................................5 2.1.2 Use Case 2: Updating Jenkins Jobs...............................5 2.1.3 Use Case 3: Working with JSON job definitions........................6 2.1.4 Use Case 4: Deleting a job...................................6 2.1.5 Use Case 5: Providing plugins info...............................6 2.2 Installation................................................6 2.2.1 Documentation.........................................7 2.2.2 Unit Tests............................................7 2.2.3 Test Coverage..........................................7 2.3 Configuration File............................................7 2.3.1 job_builder section.......................................8 2.3.2 jenkins section.........................................9 2.3.3 hipchat section.........................................9 2.3.4 stash section...........................................9 2.3.5 __future__ section.......................................9 2.4 Running.................................................9 2.4.1 Test Mode...........................................
    [Show full text]
  • Visual Build Help
    Visual Build Professional User's Manual Copyright © 1999-2021 Kinook Software, Inc. Contents I Table of Contents Part I Introduction 1 1 Overview ................................................................................................................................... 1 2 Why Visual................................................................................................................................... Build? 1 3 New Features................................................................................................................................... 2 Version 4 .......................................................................................................................................................... 2 Version 5 .......................................................................................................................................................... 3 Version 6 .......................................................................................................................................................... 4 Version 7 .......................................................................................................................................................... 7 Version 8 .......................................................................................................................................................... 9 Version 9 .........................................................................................................................................................
    [Show full text]
  • DVCS Or a New Way to Use Version Control Systems for Freebsd
    Brief history of VCS FreeBSD context & gures Is Arch/baz suited for FreeBSD? Mercurial to the rescue New processes & policies needed Conclusions DVCS or a new way to use Version Control Systems for FreeBSD Ollivier ROBERT <[email protected]> BSDCan 2006 Ottawa, Canada May, 12-13th, 2006 Ollivier ROBERT <[email protected]> DVCS or a new way to use Version Control Systems for FreeBSD Brief history of VCS FreeBSD context & gures Is Arch/baz suited for FreeBSD? Mercurial to the rescue New processes & policies needed Conclusions Agenda 1 Brief history of VCS 2 FreeBSD context & gures 3 Is Arch/baz suited for FreeBSD? 4 Mercurial to the rescue 5 New processes & policies needed 6 Conclusions Ollivier ROBERT <[email protected]> DVCS or a new way to use Version Control Systems for FreeBSD Brief history of VCS FreeBSD context & gures Is Arch/baz suited for FreeBSD? Mercurial to the rescue New processes & policies needed Conclusions The ancestors: SCCS, RCS File-oriented Use a subdirectory to store deltas and metadata Use lock-based architecture Support shared developments through NFS (fragile) SCCS is proprietary (System V), RCS is Open Source a SCCS clone exists: CSSC You can have a central repository with symlinks (RCS) Ollivier ROBERT <[email protected]> DVCS or a new way to use Version Control Systems for FreeBSD Brief history of VCS FreeBSD context & gures Is Arch/baz suited for FreeBSD? Mercurial to the rescue New processes & policies needed Conclusions CVS, the de facto VCS for the free world Initially written as shell wrappers over RCS then rewritten in C Centralised server Easy UI Use sandboxes to avoid locking Simple 3-way merges Can be replicated through CVSup or even rsync Extensive documentation (papers, websites, books) Free software and used everywhere (SourceForge for example) Ollivier ROBERT <[email protected]> DVCS or a new way to use Version Control Systems for FreeBSD Brief history of VCS FreeBSD context & gures Is Arch/baz suited for FreeBSD? Mercurial to the rescue New processes & policies needed Conclusions CVS annoyances and aws BUT..
    [Show full text]
  • Helix Authentication Service Administrator Guide 2021.1 May 2021 Copyright © 2020-2021 Perforce Software, Inc
    Helix Authentication Service Administrator Guide 2021.1 May 2021 Copyright © 2020-2021 Perforce Software, Inc.. All rights reserved. All software and documentation of Perforce Software, Inc. is available from www.perforce.com. You can download and use Perforce programs, but you can not sell or redistribute them. You can download, print, copy, edit, and redistribute the documentation, but you can not sell it, or sell any documentation derived from it. You can not modify or attempt to reverse engineer the programs. This product is subject to U.S. export control laws and regulations including, but not limited to, the U.S. Export Administration Regulations, the International Traffic in Arms Regulation requirements, and all applicable end-use, end-user and destination restrictions. Licensee shall not permit, directly or indirectly, use of any Perforce technology in or by any U.S. embargoed country or otherwise in violation of any U.S. export control laws and regulations. Perforce programs and documents are available from our Web site as is. No warranty or support is provided. Warranties and support, along with higher capacity servers, are sold by Perforce. Perforce assumes no responsibility or liability for any errors or inaccuracies that might appear in this book. By downloading and using our programs and documents you agree to these terms. Perforce and Inter-File Branching are trademarks of Perforce. All other brands or product names are trademarks or registered trademarks of their respective companies or organizations. Contents How to use
    [Show full text]
  • Staying out of the Swamp
    Staying out of the server swamp Richard Baum Perforce Software October, 2001 Contents Introduction How do I tell if I'm in the swamp? Is your system CPU bound? Is your system memory bound? Is your system I/O bound? How can Perforce cause server swamp? Network Attached Storage Confusing and complex client mappings Background processes The Perforce error log Gigantic operations Conclusion Introduction Perforce runs extremely well when it is given the right resources. A Perforce server does not generally require much CPU. Memory and disk requirements correspond to the amount of data you wish to store. Conditions can sometimes conspire to change a well-performing server into a poorly-performing one. This talk will cover some of the things to watch out for to keep your Perforce server happy and healthy. The object of this talk is to familiarize you with what to look for so you can determine where the problem lies, and what to do so you can remedy the problem. In general, performance that a user will see is limited by the I/O bandwidth of the server and the speed of its connection with a client machine. A server that appears to not be responding in its typically speedy fashion may, in fact, be swamped with data and requests for data. How do I tell if I'm in the swamp? If you suspect that your Perforce server is swamped, the first things to do are to check whether it is, in fact, running, and to examine the machine that hosts the server for any obvious signs of a problem.
    [Show full text]
  • Analiza in Prenova Sistema Upravljanja Z Dokumentacijo V Podjetju
    UNIVERZA V LJUBLJANI FAKULTETA ZA RA ČUNALNIŠTVO IN INFORMATIKO Aleksander Pahor ANALIZA IN PRENOVA SISTEMA UPRAVLJANJA Z DOKUMENTACIJO V PODJETJU Diplomsko delo na visokošolskem strokovnem študiju Mentor: dr. Mojca Ciglari č Ljubljana, 2009 I Z J A V A O A V T O R S T V U diplomskega dela Spodaj podpisani/-a ____________________________________, z vpisno številko ____________________________________, sem avtor/-ica diplomskega dela z naslovom: _________________________________________________________________________ _________________________________________________________________________ S svojim podpisom zagotavljam, da: • sem diplomsko delo izdelal/-a samostojno pod mentorstvom (naziv, ime in priimek) ___________________________________________________________________ in somentorstvom (naziv, ime in priimek) ___________________________________________________________________ • so elektronska oblika diplomskega dela, naslov (slov., angl.), povzetek (slov., angl.) ter klju čne besede (slov., angl.) identi čni s tiskano obliko diplomskega dela • soglašam z javno objavo elektronske oblike diplomskega dela v zbirki »Dela FRI«. V Ljubljani, dne ______________ Podpis avtorja/-ice:______________________ Zahvala V prvi vrsti se zahvaljujem svoji mentorici dr. Mojci Ciglari č za potrpljenje, ki ga je izkazala z menoj. Predvsem cenim to, da je bila pripravljena z nekaterimi izdelki po čakati, kar je bilo pogojeno z mojim delom, ki velikokrat ne dopuš ča, da bi se svojim ostalim obveznostim posvetil toliko, kolikor bi si zaslužile. Zahvaljujem se vsem v podjetju Hermes Softlab d.d., ki so mi vedno stali ob strani in mi pomagali odrasti strokovno, poslovno in osebno. Davorju Hvali, ki me je vzel v službo in vsem mojim nadrejenim: Alešu Pestotniku, Primožu Svetku, Mihi Urbaniji in Alešu Koširju, ki so mi zaupali vedno bolj odgovorne naloge, ki so mi omogo čile videti svet in delati na mnogih projektih in podjetjih.
    [Show full text]
  • Coverity Static Analysis
    Coverity Static Analysis Quickly find and fix Overview critical security and Coverity® gives you the speed, ease of use, accuracy, industry standards compliance, and quality issues as you scalability that you need to develop high-quality, secure applications. Coverity identifies code critical software quality defects and security vulnerabilities in code as it’s written, early in the development process when it’s least costly and easiest to fix. Precise actionable remediation advice and context-specific eLearning help your developers understand how to fix their prioritized issues quickly, without having to become security experts. Coverity Benefits seamlessly integrates automated security testing into your CI/CD pipelines and supports your existing development tools and workflows. Choose where and how to do your • Get improved visibility into development: on-premises or in the cloud with the Polaris Software Integrity Platform™ security risk. Cross-product (SaaS), a highly scalable, cloud-based application security platform. Coverity supports 22 reporting provides a holistic, more languages and over 70 frameworks and templates. complete view of a project’s risk using best-in-class AppSec tools. Coverity includes Rapid Scan, a fast, lightweight static analysis engine optimized • Deployment flexibility. You for cloud-native applications and Infrastructure-as-Code (IaC). Rapid Scan runs decide which set of projects to do automatically, without additional configuration, with every Coverity scan and can also AppSec testing for: on-premises be run as part of full CI builds with conventional scan completion times. Rapid Scan can or in the cloud. also be deployed as a standalone scan engine in Code Sight™ or via the command line • Shift security testing left.
    [Show full text]
  • Opinnäytetyö Ohjeet
    Lappeenrannan–Lahden teknillinen yliopisto LUT School of Engineering Science Tietotekniikan koulutusohjelma Kandidaatintyö Mikko Mustonen PARHAITEN OPETUSKÄYTTÖÖN SOVELTUVAN VERSIONHALLINTAJÄRJESTELMÄN LÖYTÄMINEN Työn tarkastaja: Tutkijaopettaja Uolevi Nikula Työn ohjaaja: Tutkijaopettaja Uolevi Nikula TIIVISTELMÄ LUT-yliopisto School of Engineering Science Tietotekniikan koulutusohjelma Mikko Mustonen Parhaiten opetuskäyttöön soveltuvan versionhallintajärjestelmän löytäminen Kandidaatintyö 2019 31 sivua, 8 kuvaa, 2 taulukkoa Työn tarkastajat: Tutkijaopettaja Uolevi Nikula Hakusanat: versionhallinta, versionhallintajärjestelmä, Git, GitLab, SVN, Subversion, oppimateriaali Keywords: version control, version control system, Git, GitLab, SVN, Subversion, learning material LUT-yliopistossa on tietotekniikan opetuksessa käytetty Apache Subversionia versionhallintaan. Subversionin käyttö kuitenkin johtaa ylimääräisiin ylläpitotoimiin LUTin tietohallinnolle. Lisäksi Subversionin julkaisun jälkeen on tullut uusia versionhallintajärjestelmiä ja tässä työssä tutkitaankin, olisiko Subversion syytä vaihtaa johonkin toiseen versionhallintajärjestelmään opetuskäytössä. Työn tavoitteena on löytää opetuskäyttöön parhaiten soveltuva versionhallintajärjestelmä ja tuottaa sille opetusmateriaalia. Työssä havaittiin, että Git on suosituin versionhallintajärjestelmä ja se on myös suhteellisen helppo käyttää. Lisäksi GitLab on tutkimuksen mukaan Suomen yliopistoissa käytetyin ja ominaisuuksiltaan ja hinnaltaan sopivin Gitin web-käyttöliittymä. Näille tehtiin
    [Show full text]
  • Teamcity 7.1 Documentation.Pdf
    1. TeamCity Documentation . 4 1.1 What's New in TeamCity 7.1 . 5 1.2 What's New in TeamCity 7.0 . 14 1.3 Getting Started . 26 1.4 Concepts . 30 1.4.1 Agent Home Directory . 31 1.4.2 Agent Requirements . 32 1.4.3 Agent Work Directory . 32 1.4.4 Authentication Scheme . 33 1.4.5 Build Agent . 33 1.4.6 Build Artifact . 34 1.4.7 Build Chain . 35 1.4.8 Build Checkout Directory . 36 1.4.9 Build Configuration . 37 1.4.10 Build Configuration Template . 38 1.4.11 Build Grid . 39 1.4.12 Build History . 40 1.4.13 Build Log . 40 1.4.14 Build Number . 40 1.4.15 Build Queue . 40 1.4.16 Build Runner . 41 1.4.17 Build State . 41 1.4.18 Build Tag . 42 1.4.19 Build Working Directory . 43 1.4.20 Change . 43 1.4.21 Change State . 43 1.4.22 Clean Checkout . 44 1.4.23 Clean-Up . 45 1.4.24 Code Coverage . 46 1.4.25 Code Duplicates . 47 1.4.26 Code Inspection . 47 1.4.27 Continuous Integration . 47 1.4.28 Dependent Build . 47 1.4.29 Difference Viewer . 49 1.4.30 Guest User . 50 1.4.31 History Build . 51 1.4.32 Notifier . 51 1.4.33 Personal Build . 52 1.4.34 Pinned Build . 52 1.4.35 Pre-Tested (Delayed) Commit . 52 1.4.36 Project . 53 1.4.37 Remote Run . ..
    [Show full text]
  • Main Brochure2.Indd
    Automate your Build Process . Powerful and fl exible user interface . Automate version control, compilers, install builders, deployment, testing, notifi cations, and lots more... Dynamic build process using fl ow control, iterators, loops, and exceptions . Full debugger built in - breakpoints, variable watches, live logging . Script events for every action to customise your build process Hierarchical Logging Error Handling FinalBuilder ActionStudio . The log is presented in the same . Easily detect and handle errors during . Allows development of native FinalBuilder hierarchy as your build process your build process actions . Optionally view live log output . Exception handling actions . Includes property page designer and as the build runs include: TRY, CATCH, FINALLY code editor with syntax highlighting . Builds logs are automatically . Control the fl ow of your build process . Develop actions in VBScript, JScript, COM, archived and recover from errors or any .Net language such as C#, VB.Net or Delphi for .Net . Export the log as XML, HTML, or . Unhandled errors trigger the OnFailure Text action list . Included in all editions of FinalBuilder VSoft Technologies Pty Ltd http://www.fi nalbuilder.com ABN: 82 078 466 092 P.O. Box 126, Erindale Centre, ACT 2903, Australia salesinfo@fi nalbuilder.com Phone: +61 2 6282 7488, Fax +61 2 6282 7588 news://news.fi nalbuilder.com FinalBuilder Integrates with your version control system . Microsoft TeamSystem Use a GUI instead of XML fi les . Microsoft Visual SourceSafe . Perforce Although FinalBuilder uses an XML based fi le format, you . IBM Rational ClearCase don’t need to understand it or even look at it. The FinalBuilder . QSC Team Coherence GUI allows you to quickly and easily create a build process .
    [Show full text]