Muutke küpsiste eelistusi

Testing .NET Application Blocks, First Edition [Pehme köide]

4.00/5 (3 hinnangut Goodreads-ist)
  • Formaat: Paperback / softback, 192 pages, kõrgus x laius: 229x187 mm, kaal: 1000 g
  • Ilmumisaeg: 06-Apr-2005
  • Kirjastus: Microsoft Press,U.S.
  • ISBN-10: 0735622205
  • ISBN-13: 9780735622203
Teised raamatud teemal:
  • Pehme köide
  • Hind: 26,19 €*
  • * saadame teile pakkumise kasutatud raamatule, mille hind võib erineda kodulehel olevast hinnast
  • See raamat on trükist otsas, kuid me saadame teile pakkumise kasutatud raamatule.
  • Kogus:
  • Lisa ostukorvi
  • Tasuta tarne
  • Lisa soovinimekirja
Testing .NET Application Blocks, First EditionSuurem pilt
  • Formaat: Paperback / softback, 192 pages, kõrgus x laius: 229x187 mm, kaal: 1000 g
  • Ilmumisaeg: 06-Apr-2005
  • Kirjastus: Microsoft Press,U.S.
  • ISBN-10: 0735622205
  • ISBN-13: 9780735622203
Teised raamatud teemal:
Püsilink: https://www.kriso.ee/db/9780735622203.html

Complex software environments require more in-depth testing. This book delivers the detailed guidance you need to plan and execute testing for the solutions you develop with Microsoft PATTERNS & PRACTICES application blocks. Whether you’re customizing the application blocks or integrating them into existing applications, you’ll understand the key considerations for verifying that your code meets its requirements for performance, availability, scalability, compatibility, globalization, and security features. You’ll find code examples, sample test cases, and checklists that demonstrate how to plan and implement each type of test; the guide also recommends tools to use to run the tests.

While this book was designed specifically for use in testing Microsoft PATTERNS & PRACTICES application blocks, it also provides an excellent resource for testing other .NET code.

All PATTERNS & PRACTICES guides are reviewed and approved by Microsoft engineering teams, consultants, partners, and customers—delivering accurate, real-world information that’s been technically validated and tested.

Chapter 1 Introduction 1(6)
Overview
1(1)
Why We Wrote This Guide
1(1)
Scope of This Guide
2(1)
Audience
2(1)
How to Use This Guide
3(2)
Applying the Guidance to Your Role
3(1)
Applying the Guidance to Your Application's Life Cycle
4(1)
The Team Who Brought You This Guide
5(1)
Contributors and Reviewers
5(1)
Summary
5(1)
Appendix
6(1)
Chapter 2 Testing Methodologies 7(16)
Objectives
7(1)
Overview
7(1)
Software Development Methodologies and Testing
8(5)
Waterfall Model
8(1)
Incremental or Iterative Development
9(1)
Prototyping Model
10(1)
Agile Methodology
11(1)
Extreme Programming
12(1)
Test-Driven Development
13(2)
Steps in Test-Driven Development
15(5)
Step 1: Create the Test Code
16(1)
Step 2: Write or Modify the Functional Code
17(1)
Step 3: Create Additional Tests
17(2)
Step 4: Test the Functional Code
19(1)
Step 5: Refactor the Code
19(1)
Agile Testing: Example
20(1)
Summary
21(2)
Chapter 3 Testing Process for Application Blocks 23(12)
Objective
23(1)
Overview
23(1)
Testing Process
23(9)
Input
24(1)
Steps
24(1)
Step 1: Create Test Plans
25(1)
Step 2: Review the Design
25(1)
Step 3: Review the Implementation
26(1)
Step 4: Perform Black Box Testing
27(3)
Step 5: Perform White Box Testing
30(2)
Summary
32(1)
Appendix
33(2)
Sample Test Case from a Detailed Test Plan Document
33(1)
Sample Test Case from a Detailed Test Case Document
34(1)
Chapter 4 Design Review for Application Blocks 35(20)
Objectives
35(1)
Overview
35(1)
Design Review Process
36(17)
Input
36(1)
Steps
36(1)
Step 1: Create Test Plans
37(1)
Step 2: Verify That the Design Addresses All Functional Specifications and Requirements
37(2)
Step 3: Verify That the Design Addresses All Deployment Scenarios
39(2)
Step 4: Verify That the Design Considers Performance and Scalability Tradeoffs and Best Practices
41(4)
Step 5: Verify That the Design Considers the Security Tradeoffs and Best Practices
45(1)
Step 6: Verify That the Design Uses Best Practices for Ease of Maintenance and Customization
46(2)
Step 7: Verify That the Design Addresses Globalization Issues for the Desired Cultures
48(1)
Step 8: Verify That the Design Has An Effective Exception Management Strategy
49(4)
Tools for Architecture and Design Review
53(1)
Summary
54(1)
Chapter 5 Code Review for Application Blocks 55(22)
Objective
55(1)
Overview
55(1)
Application Block Code Review
56(19)
Input
56(1)
Code Review Steps
56(2)
Step 1: Create Test Plans
58(1)
Step 2: Ensure That the Implementation Is in Accordance with the Design
59(1)
Step 3: Ensure That Naming Standards Are Followed
60(2)
Step 4: Ensure That Commenting Standards Are Followed
62(2)
Step 5: Ensure That Performance and Scalability Guidelines Are Followed
64(3)
Step 6: Ensure That Guidelines for Writing Secure Code Are Followed
67(2)
Step 7: Ensure That Globalization-related Guidelines Are Followed
69(3)
Step 8: Validate Exception Handling in the Code
72(3)
Step 9: Identify the Scenarios for More Testing
75(1)
Tools
75(1)
Summary
76(1)
Chapter 6 Black Box and White Box Testing for Application Blocks 77(22)
Objectives
77(1)
Overview
77(2)
Black Box Testing
79(9)
Input
79(1)
Black Box Testing Steps
80(1)
Step 1: Create Test Plans
81(1)
Step 2: Test the External Interfaces
81(4)
Step 3: Perform Load Testing
85(1)
Step 4: Perform Stress Testing
86(1)
Step 5: Perform Security Testing
87(1)
Step 6: Perform Globalization Testing
88(1)
White Box Testing
88(8)
Input
88(1)
White Box Testing Steps
88(2)
Step 1: Create Test Plans
90(1)
Step 2: Profile the Application Block
90(4)
Step 3: Test the Internal Subroutines
94(1)
Step 4: Test Loops and Conditional Statements
94(1)
Step 5: Perform Security Testing
95(1)
Tools
96(1)
Profiling
96(1)
Instrumentation
96(1)
Summary
97(2)
Chapter 7 Globalization Testing for Application Blocks 99(10)
Objective
99(1)
Overview
99(1)
Testing Process for Globalization
100(7)
Input
100(1)
Steps
100(1)
Step 1: Create Test Plans
101(4)
Step 2: Create the Test Environment
105(1)
Step 3: Execute Tests
105(1)
Step 4: Analyze the Results
106(1)
Summary
107(1)
Additional Resources
107(2)
Chapter 8 Performance Testing for Application Blocks 109(16)
Objectives
109(1)
Overview
109(2)
Performance Objectives
111(1)
Load Testing
112(7)
Input
112(1)
Load Testing Steps
112(1)
Step 1: Identify Key Scenarios
113(1)
Step 2: Identify Workload
113(3)
Step 3: Identify Metrics
116(1)
Step 4: Create Test Cases
117(1)
Step 5: Simulate Load
118(1)
Step 6: Analyze the Results
118(1)
Stress Testing
119(4)
Input
119(1)
Stress Testing Steps
119(1)
Step 1: Identify Key Scenarios
120(1)
Step 2: Identify Workload
120(1)
Step 3: Identify Metrics
121(1)
Step 4: Create Test Cases
121(1)
Step 5: Simulate Load
122(1)
Step 6: Analyze the Results
122(1)
Tools
123(1)
Load Simulators and Generators
123(1)
Performance Monitoring Tools
123(1)
Summary
124(1)
Chapter 9 Integration Testing for Application Blocks 125(34)
Objectives
125(1)
Overview
125(4)
Sample Application Block
126(1)
Sample Business Application
126(3)
Unit Testing a Customized Application Block
129(7)
Step 1: Create Test Plans
130(1)
Step 2: Review the Design
131(1)
Step 3: Review the Implementation
132(1)
Step 4: Perform Black Box Testing
133(1)
Step 5: Perform White Box Testing
134(1)
Step 6: Regression Test the Existing Functionality
135(1)
More Information
136(1)
Integration Testing an Application Block
136(19)
Input for Integration Testing
137(1)
Steps for Integration Testing
138(1)
Step 1: Create Test Plans
139(1)
Step 2: Perform Code Review of the Application Modules That Integrate the Application Block
139(1)
Step 3: Execute the Use Cases of the Application
140(3)
Step 3: Perform Load Testing
143(6)
Step 4: Perform Stress Testing
149(4)
Step 5: Perform Globalization Testing
153(1)
Step 6: Perform Security Testing
154(1)
Summary
155(1)
Appendix
156(3)
Index 159(8)
Additional Resources 167


Developed by senior editors and content managers at Microsoft Corporation.