application lifecycle management utilizando ferramentas microsoft

© 2015 Stefanini Proprietary and Confidential

1

ApplicationLifecycle

ManagementAgile Project Management

in Visual Studio Team Foundation Server 2013


2

Luis Cesar TeodoroArquiteto de Soluções na Stefanini

Sou Arquiteto de software, entusiasta DevOPs, especialista plataforma Microsoft por formação(MCSA, MCPD), Scrum Master por formação (CSM), consultor, palestrante e instrutor. Trabalho com TI há cerca de 15 anos, gosto muito de documentar e compartilhar o que tenho aprendido. Além disto tudo, sou casado, pai da Laura e do Mateus. Fique a vontade para entrar em contato :)

Microsoft Certified Solutions Expert: SharePoint

Microsoft Certified Solutions Developer: SharePoint, Web

CSM: Certified ScrumMaster®

Contato: [email protected]: https://br.linkedin.com/in/luís-cesar-teodoro-298a6116

mailto:[email protected]

https://br.linkedin.com/in/luís-cesar-teodoro-298a6116

Application Lifecycle ManagementAgile Project Management in Visual Studio Team Foundation Server 2013


3

Application Lifecycle Management



4

Branching and Merging Visualization with Visual Studio Team Foundation Server 2013

Log in as Julia. All user passwords are P2ssw0rd



5

Branching and Merging Visualization

1. Log in as Julia. A senha para todos os usuário é:

P2ssw0rd.

2. Abrir o Visual studio Start Menu | All Programs |

Microsoft Visual Studio 2013 | Visual Studio

2013.

3. Abrir o Source Control Explorer window from

View | Other Windows | Source Control

Explorer.



6


1. Clicar com o botão direito na branch:

Release1 Selecionar Advanced

|Properties no menu. Essas

propriedades provem detalhes como:

Versões, Descrições, hierarquias com

outras brachs e permissões.



7


1. Abra a solution abaixo.



8


1. Abra a solution abaixo.

2. Rebuild Solution

3. Selecione o projeto

FabrikamFiber.Web e set

as the startup project

(right-click and select Set

as StartUp Project in

Solution Explorer).

Pressione Ctrl+F5 Para Rodarthe Fabrikam Fiber intranet portal.



9




10


1. Ao Clicar o link estará

quebrado levando o usuário a

tela de erro



11


1. Feche o Internet Explorer e retorne ao

Visual Studio.

2. A tarefa sera atualizar a branch Release1 e

executar um deploy no servidor de

produção. Apartir da Solution Explorer, abra

_Profile.cshtml contido em

FabrikamFiber.Web | Views | Shared pasta

contida na branch release1.

3. Localize o trecho de código e comente

conforme imagem.



12


1. Pressione Ctrl+F5 para rodar o website e se

a funcionalidade está OK.

2. Open the Pending Changes window from

View | Other Windows | Pending

Changes.

3. In the Comment field, enter “removed

non-functional links from profile”, verify

only _Profile.cshtml is changed, and select the

Check In button.



13


1. In Source Control

Explorer, right-click on

the Release1 branch and

select View History from

the context menu.



14


1. Right-click on the

changeset that you

just checked in and

select Track

Changeset from the

context menu.



15




16


1. To perform the merge of this

changeset and the Main branch,

drag and drop the green Release1

node onto the Main node. This

will load the Source Control

Merge Wizard.



17




18


1. After the merge is complete, open the Pending

Changes window on the right and note that

_Profile.cshtml changed status for the Main code

branch and is now “merge, edit”. The merge

process is complete, but we still need to check in

the changes.



19


1. Add a Comment of “Merging fast-tracked changes

from Release to Main” and then click the Check In

button to finalize the merge.



20


1. In the Tracking Changeset window, click on the

Rerun button to generate an updated view. You

will need to click the Visualize button again when

the Select Branches window appears.



21


1. Next, merge the changeset from the Main branch

with the Dev branch in the same manner as

before by dragging and dropping to load the

Source Control Merge Wizard.

2. Select Next followed by Finish to perform the

merge process.

3. In the Pending Changes window, enter a

Comment of “Merged fast-tracked changes from

Main to Dev”.

4. Select the Check In button to finalize the merge

with the Dev branch.

5. In the Tracking Changeset window, click on the

Rerun button to see the updated view.



22




23


1. In Solution Explorer, navigate to

and right-click on the

_Profile.cshtml file and select

Source Control | Annotate from

the context menu.

2. Scroll to the bottom of the

annotated _Profile.cshtml file

and locate the HTML that you

previously commented out.

3. In the annotation column on the

left-hand side, mouse over the

recent changeset (it should

show the date of the guest

virtual machine). Note that the

changeset path and comment

refer to the Production branch

where the original change was

made.



24

Agile Teams



25

Agile Teams

Time 1- Integrantes

- Usuario …- Funcionalidades

-

Time 2- Integrantes


-

Time 3- Integrantes


-

Time 4- Integrantes


-



26

Product Backlog and Sprints




27





28




29


⦁ Nota: Cada Equipe pode ter

diferente itens listados no item

favoritos e diferentes work items.



30




31




32




33




34




35




36




37




38




39




40




41




42


⦁ Gráfico que indica a velocidade

em que o time completou as

histórias contidas no sprint.



43




44




45




46




47




48




49




50


⦁ Cumulative Flow Diagram



51


⦁ Nota: Esse Cumulative Flow Diagram é

a representação de um cenário tipico

de desenvolvimento de software.



52




53




54

Nota: Para mais informações de como usar o

“Kanban board”, por favor acesse: “Manage

Your Backlog with the Kanban Board”.


http://msdn.microsoft.com/en-us/library/vstudio/jj838789.aspx



55




56




57




58




59




60




61




62




63




64




65




66




67

Authoring and Running Manual Tests using Microsoft Test Manager 2013




68

Authoring and Running Manual Tests

1. Log in as Julia. All user passwords are P2ssw0rd.

2. Open Microsoft Test Manager from Start | All

Programs | Microsoft Visual Studio 2013 |

Microsoft Test Manager.

3. In this lab, we’re going to focus on creating a new

manual test case and running it. We will focus on

the other aspects of managing test cases and test

plans in another lab.

4. If you are not in the Test plan view already, click

on Plan from the main menu. The Microsoft Test

Manager will connect to the most recently loaded

test plan, which in the case of this virtual machine

is the test plan named Iteration 2. If Iteration 2

plan is not opened, click on the Home button to

switch to Iteration 2.



69




70


1. In the Title box, type “Confirm that receipt

number appears after successful order”.

Alternatively, you can open the “New Test

Case.txt” file from the Code Snippets folder on

the desktop of the VM and copy and paste the

title from there.

2. At this point, we’re ready to add steps to this

manual test. Each step includes an Action, which

describes the action the tester needs to perform.

Optionally, a step can include an Expected Result,

which describes the expected result of the given

action.

3. In the Steps panel, create a step for each of the

following Actions, only one of which has an

Expected Result. See the next paragraph for an

alternate, faster way to add the actions.

Action Expected Result

Open

http://www.tailspinto

ys.com

Click Model Airplanes

Click Northwind Trader

Click Add to Cart

Click Checkout

Enter @First, @Last,

@Email, @Address,

@City, @Country,

@State, @PostalCode

Click Review Order

Click Place Order

Confirm order page has

receipt #

Receipt # should appear

at top of order

confirmation page

Close Browser



71


An alternative to manual entry of each step is to copy and paste all steps

from the “New Test Case.txt” file to add them all at once. In order to do

this, right-click on the row that currently shows “Click here to add a step”

and select the Paste option.



72


1. Note the “Enter @First, @Last,

@Email, @Address, @City,

@Country, @State,

@PostalCode” step. In this

step, we used the @ sign to

indicate that there were

iteration-specific variables to

be used during the manual

test pass. We can define which

variables to use by scrolling

down to the Parameter Values

section of this form and

entering them for each

iteration. Use the following

table to set up values for three

iterations (or use the copy and

paste method from the “New

Test Case.txt” file once again):



73


First Last Email Address

Michael Affronti [email protected] One Microsoft Way

Chris Barry [email protected] Two Tailspin Trail

Robin Wood [email protected] Nine Northwind Street

City Country State PostalCode

Redmond USA Washington 98052

Springfield USA Illinois 11135

North Wind USA North Dakota 99909



74




75




76




77




78




79




80




81


1. In this iteration, we will not create an action

recording as it will overwrite the original one that

we just created. Instead, we’re going to use the

version that we just recorded to aid in the running

of this iteration. Click the Start Test button to start

iteration 2.

2. Step 1 should already be selected. Hold down the

Shift key and click the “Click Place Order” step to

select all steps leading to it, inclusively.



82




83




84




85




86




87




88


Test Case Management and Manual Testing in Team Foundation Server 2013 Web Access



89




90




91




92




93


⦁ Note: As of Update 2, you

cannot add or edit

parameters using TFS Web

Access. You will need to

use Microsoft Test

Manager for this purpose.



94




95




96




97




98




99

Relatórios

https://msdn.microsoft.com/en-us/library/dd380714(v=vs.110).aspx Bug Status

Bug Trends

Build Quality Indicators

Build Success Over Time

Build Summary

Burndown and Burn Rate

Reactivations

Remaining Work

Status on All Iterations

Stories Overview

Stories Progress

Test Case Readiness

Test Plan Progress

Test Plan Progress

Unplanned Work

https://msdn.microsoft.com/en-us/library/dd380714(v=vs.110).aspx















https://msdn.microsoft.com/en-us/library/ee707132(v=vs.110).aspx



100

Links Uteis

Caminho para Virtual Machine e Hands on Lab- Application Lifecycle Management Virtual Machine And Hands on Labs

http://blogs.msdn.com/b/briankel/archive/2013/08/02/visual-studio-2013-application-lifecycle-management-virtual-machine-and-hands-on-labs-demo-scripts.aspx

Ou

http://goo.gl/BCHtbq

http://www.microsoftvirtualacademy.com/

http://onthehub.com/



http://goo.gl/BCHtbq

http://www.microsoftvirtualacademy.com/

http://onthehub.com/

OBRIGADO!

Luis Cesar Teodoro

Arquiteto de Soluções

[email protected]


101

Dream big, work smart,

deliver fast.

application lifecycle management utilizando ferramentas microsoft

Technology