Domain nerdblogs.de kaufen?

Produkte zum Begriff Testing:


  • Effective Software Testing
    Effective Software Testing

    Effective Software Testing is a hands-on guide to creating high quality tests, from your first line of code through pre-delivery checks. It's full of techniques drawn from proven research in software engineering. You'll learn to efficiently engineer tests specifically for your software and end reliance on generic testing practices that may be right for every project. Each chapter puts a new technique into practice with source code samples, real-world tradeoffs, and answers to the common questions developers pose about testing. You'll learn how to scrutinize your requirements for potential tests, generate tests from your code structure, and engineer rigorous suites of unit, integration, and system tests.Go beyond unit tests! Great software testing makes the entire development process more efficient, from understanding your code before you write it to catching bugs in tricky corner cases.Effective Software Testing teaches you a systematic approach to software testing. You'll master easy-to-apply techniques to create strong test suites that are specifically engineered for your code. Following real-world use cases and detailed code samples, you'll soon be engineering tests that find the bugs hiding in edge cases and the parts of code you would never think of testing! Along the way, you'll develop an intuition for testing that can save years of learning by trial and error.

    Preis: 47.07 € | Versand*: 0 €
  • Software Testing with Visual Studio 2010
    Software Testing with Visual Studio 2010

    Use Visual Studio 2010’s Breakthrough Testing Tools to Improve Quality Throughout the Entire Software Lifecycle   Together, Visual Studio 2010 Ultimate, Visual Studio Test Professional 2010, Lab Management 2010, and Team Foundation Server offer Microsoft developers the most sophisticated, well-integrated testing solution they’ve ever had. Now, Microsoft MVP and VS testing guru Jeff Levinson shows exactly how to use Microsoft’s new tools to save time, reduce costs, and improve quality throughout the entire development lifecycle.   Jeff demonstrates how Microsoft’s new tools can help you finally overcome long-standing communication, coordination, and management challenges. You’ll discover how to perform first-rate functional testing; quickly create and execute tests and record the results with log files and video; and create bugs directly from tests, ensuring reproducibility and eliminating wasted time. Levinson offers in-depth coverage of Microsoft’s powerful new testing metrics, helping you ensure traceability all the way from requirements through finished software.   Coverage includes   •    Planning your tests using Microsoft Test Manager (MTM) •    Creating test settings, structuring test cases, and managing the testing process •    Executing manual tests with Microsoft Test Manager and Test Runner •    Filing and resolving bugs, and customizing your bug reporting process •    Automating test cases and linking automated tests with requirements •    Executing automated test cases through both Visual Studio and Microsoft Test Manager •    Integrating automated testing into the build process •    Using Microsoft’s Lab Management virtualization platform to test applications, snapshot environments, and reproduce bugs •    Implementing detailed metrics for evaluating quality and identifying improvements   Whether you’re a developer, tester, manager, or analyst, this book can help you significantly improve the way you work and the results you deliver—both as an individual right now, and as a team member throughout your entire project.  

    Preis: 27.81 € | Versand*: 0 €
  • Software Testing with Visual Studio 2010
    Software Testing with Visual Studio 2010

    Use Visual Studio 2010’s Breakthrough Testing Tools to Improve Quality Throughout the Entire Software Lifecycle   Together, Visual Studio 2010 Ultimate, Visual Studio Test Professional 2010, Lab Management 2010, and Team Foundation Server offer Microsoft developers the most sophisticated, well-integrated testing solution they’ve ever had. Now, Microsoft MVP and VS testing guru Jeff Levinson shows exactly how to use Microsoft’s new tools to save time, reduce costs, and improve quality throughout the entire development lifecycle.   Jeff demonstrates how Microsoft’s new tools can help you finally overcome long-standing communication, coordination, and management challenges. You’ll discover how to perform first-rate functional testing; quickly create and execute tests and record the results with log files and video; and create bugs directly from tests, ensuring reproducibility and eliminating wasted time. Levinson offers in-depth coverage of Microsoft’s powerful new testing metrics, helping you ensure traceability all the way from requirements through finished software.   Coverage includes   •    Planning your tests using Microsoft Test Manager (MTM) •    Creating test settings, structuring test cases, and managing the testing process •    Executing manual tests with Microsoft Test Manager and Test Runner •    Filing and resolving bugs, and customizing your bug reporting process •    Automating test cases and linking automated tests with requirements •    Executing automated test cases through both Visual Studio and Microsoft Test Manager •    Integrating automated testing into the build process •    Using Microsoft’s Lab Management virtualization platform to test applications, snapshot environments, and reproduce bugs •    Implementing detailed metrics for evaluating quality and identifying improvements   Whether you’re a developer, tester, manager, or analyst, this book can help you significantly improve the way you work and the results you deliver—both as an individual right now, and as a team member throughout your entire project.  

    Preis: 20.32 € | Versand*: 0 €
  • Developer Testing: Building Quality into Software
    Developer Testing: Building Quality into Software

    How do successful agile teams deliver bug-free, maintainable software—iteration after iteration? The answer is: By seamlessly combining development and testing. On such teams, the developers write testable code that enables them to verify it using various types of automated tests. This approach keeps regressions at bay and prevents “testing crunches”—which otherwise may occur near the end of an iteration—from ever happening. Writing testable code, however, is often difficult, because it requires knowledge and skills that cut across multiple disciplines.   In Developer Testing, leading test expert and mentor Alexander Tarlinder presents concise, focused guidance for making new and legacy code far more testable. Tarlinder helps you answer questions like: When have I tested this enough? How many tests do I need to write? What should my tests verify? You’ll learn how to design for testability and utilize techniques like refactoring, dependency breaking, unit testing, data-driven testing, and test-driven development to achieve the highest possible confidence in your software. Through practical examples in Java, C#, Groovy, and Ruby, you’ll discover what works—and what doesn’t.   You can quickly begin using Tarlinder’s technology-agnostic insights with most languages and toolsets while not getting buried in specialist details. The author helps you adapt your current programming style for testability, make a testing mindset “second nature,” improve your code, and enrich your day-to-day experience as a software professional. With this guide, you will Understand the discipline and vocabulary of testing from the developer’s standpointBase developer tests on well-established testing techniques and best practicesRecognize code constructs that impact testabilityEffectively name, organize, and execute unit testsMaster the essentials of classic and “mockist-style” TDDLeverage test doubles with or without mocking frameworksCapture the benefits of programming by contract, even without runtime support for contractsTake control of dependencies between classes, components, layers, and tiersHandle combinatorial explosions of test cases, or scenarios requiring many similar testsManage code duplication when it can’t be eliminatedActively maintain and improve your test suitesPerform more advanced tests at the integration, system, and end-to-end levelsDevelop an understanding for how the organizational context influences quality assuranceEstablish well-balanced and effective testing strategies suitable for agile teams

    Preis: 32.09 € | Versand*: 0 €
  • Warum ist Software Testing wichtig?

    Warum ist Software Testing wichtig? Software Testing ist wichtig, um sicherzustellen, dass die Software fehlerfrei funktioniert und den Anforderungen der Benutzer entspricht. Durch gründliches Testing können potenzielle Probleme frühzeitig erkannt und behoben werden, was letztendlich die Qualität der Software verbessert. Zudem trägt Software Testing dazu bei, das Vertrauen der Benutzer in die Software zu stärken und die Kundenzufriedenheit zu erhöhen. Nicht zuletzt hilft Testing auch dabei, Kosten und Zeit im Entwicklungsprozess zu sparen, da Fehler frühzeitig identifiziert und behoben werden können. Insgesamt ist Software Testing also ein entscheidender Schritt, um eine zuverlässige und hochwertige Software bereitzustellen.

  • Was ist der Unterschied zwischen Blackbox-Testing und Whitebox-Testing in der Programmierung?

    Blackbox-Testing bezieht sich auf eine Testmethode, bei der der Tester keine Kenntnisse über den internen Aufbau oder die Implementierung des Programms hat. Stattdessen werden nur die Ein- und Ausgabewerte getestet, um sicherzustellen, dass das Programm wie erwartet funktioniert. Whitebox-Testing hingegen bezieht sich auf eine Testmethode, bei der der Tester Kenntnisse über den internen Aufbau und die Implementierung des Programms hat. Dies ermöglicht es dem Tester, gezielt bestimmte Pfade und Bedingungen im Code zu testen, um mögliche Fehler zu finden.

  • Wie kann die Effektivität von Software-Testing verbessert werden?

    Die Effektivität von Software-Testing kann verbessert werden, indem automatisierte Tests implementiert werden, um wiederholbare Testszenarien abzudecken. Zudem ist es wichtig, frühzeitig in den Entwicklungsprozess zu integrieren, um Fehler frühzeitig zu erkennen und zu beheben. Eine kontinuierliche Verbesserung der Testprozesse durch regelmäßiges Feedback und Analyse der Testergebnisse ist ebenfalls entscheidend.

  • Was sind die grundlegenden Unterschiede zwischen manuellem Testing und automatisiertem Testing?

    Manuelles Testing wird von Testern durchgeführt, die manuell Testfälle ausführen, während automatisiertes Testing mithilfe von Tools und Skripten automatisiert wird. Automatisiertes Testing ist schneller, wiederholbar und effizienter als manuelles Testing. Manuelles Testing erfordert menschliche Interaktion und Urteilsvermögen, während automatisiertes Testing vordefinierte Tests ausführt.

Ähnliche Suchbegriffe für Testing:


  • Developer Testing: Building Quality into Software
    Developer Testing: Building Quality into Software

    How do successful agile teams deliver bug-free, maintainable software—iteration after iteration? The answer is: By seamlessly combining development and testing. On such teams, the developers write testable code that enables them to verify it using various types of automated tests. This approach keeps regressions at bay and prevents “testing crunches”—which otherwise may occur near the end of an iteration—from ever happening. Writing testable code, however, is often difficult, because it requires knowledge and skills that cut across multiple disciplines.   In Developer Testing, leading test expert and mentor Alexander Tarlinder presents concise, focused guidance for making new and legacy code far more testable. Tarlinder helps you answer questions like: When have I tested this enough? How many tests do I need to write? What should my tests verify? You’ll learn how to design for testability and utilize techniques like refactoring, dependency breaking, unit testing, data-driven testing, and test-driven development to achieve the highest possible confidence in your software. Through practical examples in Java, C#, Groovy, and Ruby, you’ll discover what works—and what doesn’t.   You can quickly begin using Tarlinder’s technology-agnostic insights with most languages and toolsets while not getting buried in specialist details. The author helps you adapt your current programming style for testability, make a testing mindset “second nature,” improve your code, and enrich your day-to-day experience as a software professional. With this guide, you will Understand the discipline and vocabulary of testing from the developer’s standpointBase developer tests on well-established testing techniques and best practicesRecognize code constructs that impact testabilityEffectively name, organize, and execute unit testsMaster the essentials of classic and “mockist-style” TDDLeverage test doubles with or without mocking frameworksCapture the benefits of programming by contract, even without runtime support for contractsTake control of dependencies between classes, components, layers, and tiersHandle combinatorial explosions of test cases, or scenarios requiring many similar testsManage code duplication when it can’t be eliminatedActively maintain and improve your test suitesPerform more advanced tests at the integration, system, and end-to-end levelsDevelop an understanding for how the organizational context influences quality assuranceEstablish well-balanced and effective testing strategies suitable for agile teams

    Preis: 24.6 € | Versand*: 0 €
  • Best Practices for the Formal Software Testing Process: A Menu of Testing Tasks
    Best Practices for the Formal Software Testing Process: A Menu of Testing Tasks

    This is the digital version of the printed book (Copyright © 2004).Testing is not a phase. Software developers should not simply throw software over the wall to test engineers when the developers have finished coding. A coordinated program of peer reviews and testing not only supplements a good software development process, it supports it.   A good testing life cycle begins during the requirements elucidation phase of software development, and concludes when the product is ready to install or ship following a successful system test.   Nevertheless, there is no one true way to test software; the best one can hope for is to possess a formal testing process that fits the needs of the testers as well as those of the organization and its customers.   A formal test plan is more than an early step in the software testing process—it's a vital part of your software development life cycle. This book presents a series of tasks to help you develop a formal testing process model, as well as the inputs and outputs associated with each task. These tasks include:   review of program plansdevelopment of the formal test plancreation of test documentation (test design, test cases, test software, and test procedures)acquisition of automated testing toolstest executionupdating the test documentationtailoring the model for projects of all sizes   Whether you are an experienced test engineer looking for ways to improve your testing process, a new test engineer hoping to learn how to perform a good testing process, a newly assigned test manager or team leader who needs to learn more about testing, or a process improvement leader, this book will help you maximize your effectiveness.  

    Preis: 9.62 € | Versand*: 0 €
  • Best Practices for the Formal Software Testing Process: A Menu of Testing Tasks
    Best Practices for the Formal Software Testing Process: A Menu of Testing Tasks

    This is the digital version of the printed book (Copyright © 2004).Testing is not a phase. Software developers should not simply throw software over the wall to test engineers when the developers have finished coding. A coordinated program of peer reviews and testing not only supplements a good software development process, it supports it.   A good testing life cycle begins during the requirements elucidation phase of software development, and concludes when the product is ready to install or ship following a successful system test.   Nevertheless, there is no one true way to test software; the best one can hope for is to possess a formal testing process that fits the needs of the testers as well as those of the organization and its customers.   A formal test plan is more than an early step in the software testing process—it's a vital part of your software development life cycle. This book presents a series of tasks to help you develop a formal testing process model, as well as the inputs and outputs associated with each task. These tasks include:   review of program plansdevelopment of the formal test plancreation of test documentation (test design, test cases, test software, and test procedures)acquisition of automated testing toolstest executionupdating the test documentationtailoring the model for projects of all sizes   Whether you are an experienced test engineer looking for ways to improve your testing process, a new test engineer hoping to learn how to perform a good testing process, a newly assigned test manager or team leader who needs to learn more about testing, or a process improvement leader, this book will help you maximize your effectiveness.  

    Preis: 7.48 € | Versand*: 0 €
  • Automated Software Testing: Introduction, Management, and Performance
    Automated Software Testing: Introduction, Management, and Performance

    With the urgent demand for rapid turnaround on new software releases--without compromising quality--the testing element of software development must keep pace, requiring a major shift from slow, labor-intensive testing methods to a faster and more thorough automated testing approach. Automated Software Testing is a comprehensive, step-by-step guide to the most effective tools, techniques, and methods for automated testing. Using numerous case studies of successful industry implementations, this book presents everything you need to know to successfully incorporate automated testing into the development process. In particular, this book focuses on the Automated Test Life Cycle Methodology (ATLM), a structured process for designing and executing testing that parallels the Rapid Application Development methodology commonly used today. Automated Software Testing is designed to lead you through each step of this structured program, from the initial decision to implement automated software testing through test planning, execution, and reporting. Included are test automation and test management guidance for: Acquiring management support Test tool evaluation and selection The automated testing introduction process Test effort and test team sizing Test team composition, recruiting, and management Test planning and preparation Test procedure development guidelines Automation reuse analysis and reuse library Best practices for test automation

    Preis: 32.09 € | Versand*: 0 €
  • Was sind die wichtigsten Methoden für das Testing von Software?

    Die wichtigsten Methoden für das Testing von Software sind manuelles Testing, automatisiertes Testing und exploratives Testing. Manuelles Testing beinhaltet das manuelle Überprüfen der Software auf Fehler und Funktionalität. Automatisiertes Testing verwendet Tools und Skripte, um wiederholbare Tests durchzuführen. Exploratives Testing beinhaltet das Erkunden der Software, um unerwartete Fehler zu finden.

  • Was sind die gängigsten Methoden zur Durchführung von Software-Testing?

    Die gängigsten Methoden zur Durchführung von Software-Testing sind manuelles Testing, automatisiertes Testing und exploratives Testing. Beim manuellen Testing werden Tests von Hand durchgeführt, während beim automatisierten Testing Tools verwendet werden, um Tests automatisch auszuführen. Beim explorativen Testing wird die Software ohne vorher festgelegte Testfälle getestet, um unerwartete Fehler zu finden.

  • Was sind die wichtigsten Methoden für das Testing von Software?

    Die wichtigsten Methoden für das Testing von Software sind manuelles Testing, automatisiertes Testing und exploratives Testing. Beim manuellen Testing überprüfen Tester die Software manuell auf Fehler und Funktionalität. Beim automatisierten Testing werden Testskripte erstellt, um wiederholbare Tests automatisch durchzuführen. Beim explorativen Testing wird die Software ohne vorher festgelegte Testfälle getestet, um unerwartete Fehler zu entdecken.

  • Was sind die gängigsten Methoden für das Testing von Software-Anwendungen?

    Die gängigsten Methoden für das Testing von Software-Anwendungen sind manuelles Testing, automatisiertes Testing und exploratives Testing. Beim manuellen Testing überprüfen Tester die Software manuell auf Fehler und Funktionalität. Beim automatisierten Testing werden Tests automatisiert durchgeführt, um Effizienz und Genauigkeit zu erhöhen. Exploratives Testing beinhaltet das freie Erkunden der Software, um unerwartete Fehler zu entdecken.

* Alle Preise verstehen sich inklusive der gesetzlichen Mehrwertsteuer und ggf. zuzüglich Versandkosten. Die Angebotsinformationen basieren auf den Angaben des jeweiligen Shops und werden über automatisierte Prozesse aktualisiert. Eine Aktualisierung in Echtzeit findet nicht statt, so dass es im Einzelfall zu Abweichungen kommen kann.