Mva stf module 3 - rus

  • Published on
    13-Feb-2017

  • View
    458

  • Download
    2

Transcript

PowerPoint Presentation | 1 01 | 1.1 1.2 1.3 1.4 04 | 4.1 4.2 Agile 4.3 02 | 2.1 2.2 2.3 05 | 5.1 5.2 5.3 03 | 3.1 3.2 3.3 3.4 3.5 06 | 6.1 6.2 6.3 6.4 203 | Click to edit Master subtitle style3 Appropriately Scoping Test Cases43.1 3.2 03 | 5 : , , Testing hooks ( )6 ? ? ? 7 . , . . / agile , . .8 . 9 . , . :10 . , . Microsoft Visual Studio . Visual Studio , .11 , . , . , . , . , .12 (TDD) . , . , . : . - .. . . .13 14Testing Hooks ( )Testing hook , ., .Hooks .15 , . , "" . , , .16 ? ? ? 173.3 03 | 18 : 19 (ALM)? Microsoft Visual Studio? ?20 , .Microsoft Visual Studio ALM ; Microsoft Visual Studio Team Foundation Server (TFS).TFS , , .21ALM 22ALM Visual StudioPowerPoint (Storyboarding): , PowerPoint .Product backlog: product backlog .Sprint backlog team capacity: sprint backlog , , , , .Task board: , .Request Feedback Microsoft Feedback Client: .23 . , agile. , . : . agile . . , /.24 (Code Coverage) . . ., 80% . . Visual Studio, : (Block coverage) (Line coverage)25 Visual Studio26 (ALM)? Microsoft Visual Studio? ?273.3 03 | 28 : . Featur Testshttps://wiki.documentfoundation.org/QA/Testing/Feature_Tests/ru29 ? ? ? 30 (feature, ) , . . . , , . . , ., . , , , Microsoft Word.31 , ., , , . . , . While well-designed unit and integration tests may provide excellent code coverage and help ensure the units work meet the internal specifications of the developers, it is important that the functionality of each feature is tested.Each feature in an application should be tested independently.A test that focuses on the functionality of an individual feature in the software, independent of other features, is called a feature test. In many cases, black box testing is used to testing functionalityThe big-picture goal of feature testing is to ensure the features implemented in the software meet or fit the user requirements.32 (ad hoc) , . , , . . . .33 . . , , , . , .34 (UI) UI ., , , , UI . UI (coded UI tests).Visual Studio UI .35 ? ? ? 363.5 03 | 37 : : 38 ? ? ? 39 , , ., , . , ! , , . , .40 TDD, agile, , . , ., -, / , , . (happy path test). , , , ., ?41 , ., . , ().42 . ., (1 , 2 , ..), , 13? 12 ( ), , . , , . 43 , , . , .Visual Studio .44 : . . . .45 , . , : -.46 ? ? ? 47 MSDN Software Testing ResourcesModeling User Requirementshttp://msdn.microsoft.com/en- us/library/vstudio/dd409376.aspxUser Story (Agile)http://msdn.microsoft.com/en- us/library/dd380634.aspxTesting Methodologieshttp://msdn.microsoft.com/en- us/library/ff649520.aspxTesting in the Software Lifecyclehttp://msdn.microsoft.com/en-us/library/jj159342.aspxCreating, Editing and Maintaining a Coded UI Testhttp://msdn.microsoft.com/en-us/library/ff977233.aspxCreating and Running Unit Tests for Managed Codehttp://msdn.microsoft.com/en- us/library/ms182532.aspxManual System Testshttp://msdn.microsoft.com/library/jj15933 4.aspxTest Automation Code Review Guidelineshttp://msdn.microsoft.com/en- us/library/ff519670.aspx48