Practical development environments

This book doesn't tell you how to write faster code, or how to write code with fewer memory leaks, or even how to debug code at all. What it does tell you is how to build your product in better ways, how to keep track of the code that you write, and how to track the bugs in your code. Plus som...

Descripción completa

Detalles Bibliográficos
Autor principal: Doar, Matthew (-)
Formato: Libro electrónico
Idioma:Inglés
Publicado: Beijing ; Sebastopol, California : O'Reilly 2005.
Edición:First edition
Materias:
Ver en Biblioteca Universitat Ramon Llull:https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627125106719
Tabla de Contenidos:
  • Table of Contents; List of Figures; List of Tables; List of Examples; Preface; What This Book Is About; What This Book Is Not About; Who Should Read This Book; What's Inside; Style Conventions; Using Code Examples; Safari Enabled; Comments and Questions; Acknowledgments; Introduction; Developing Software Products; Open and Closed Software Development; Dirty Secrets of Software Projects; What Does "Practical" Mean?; A Personal Tools Quiz; Project Basics; The Parts of a Project; Software Configuration Management; Building Software; Testing Software; Tracking Bugs; Writing Documentation
  • Releasing ProductsMaintenance; Recommended Tools; Modern Environments; Classic Environments; Future Environments; Project Concepts; Preconstructed Development Environments; SourceForge; GForge; CollabNet; Savane; BerliOS; Improving PDEs; Why Integration Is Helpful; Why Automation Is Vital; Automation Environments; Shell Scripts and Batch Files; Tinderbox; Anthill; CruiseControl; Labeling Builds; Naming Projects and Machines; Choosing Project Names; Choosing Machine Names; Choosing New Tools; Steps When Changing Tools; Internationalization and Localization
  • Authentication, Authorization, and AccountingSoftware Configuration Management; Why Do I Need SCM?; What SCM Is and Is Not; Drawbacks of SCM; A Typical Day's Work with SCM; SCM Annoyances; Branches and Tags; When to Branch? When to Tag?; Naming Branches and Tags; Merge Madness; Security; Access Wars; Filenames to Avoid; Backups and SCM; Backing up CVS; SCM Tools; CVS; Making your life with CVS easier; Subversion; Arch; Perforce; BitKeeper; ClearCase; Visual SourceSafe; Comparison of SCM Tools; Wider Uses of SCM; Checklist; Building Software; How Software Gets Built
  • The Different Stages of a BuildA Typical Build File; Build States: Virgin, Up-to-date, Changed, Interrupted, Clean; Good Builds, Bad Builds; Build States and Different Targets; Build States in Practice; Build Dependencies; When Build Dependencies Go Wrong; How Build Dependencies Change; Common Build Problems; Slow Builds; Build Tools; Shell Scripts and Batch Files; make; GNU Autotools; Autoconf; Automake; Libtool; An Autotools "Hello World" program; Debugging GNU Autotools installs; More Autotools; Ant; Jam; SCons; Custom Build Tools; Comparison of Build Tools; Changing Your Build Tool
  • ChecklistTesting Software; Different Kinds of Tests; Unit Tests; System Tests; Customer Tests; Other Tests; Why Automate Your Tests?; Evaluating Test Environments; Preparing to Test; Running the Tests; After the Tests; Good Test Reports; Test Environments; Shell Scripts and Batch Files; xUnit; DejaGnu; SilkTest; Types of Test Tools; Memory Analyzers; Coverage Tools; Performance Tools; Static Code Analyzers; The Difficult Parts of Testing; Faults of Omission; Capturing Output; Using Multiple Machines; Sending commands; Starting the tests; Collecting the data; Only a Developer Can Do That!
  • Accessibility Testing