New Joiners Document

Contents

New Joiners Document........................................................................................... 1

1. Access Details.............................................................................................. 2
1.1 VSTF Installation.................................................................................... 2
1.2 MTM Access........................................................................................... 6
1.3 SAP GUI Log on pad installation.............................................................7
1.4 SAP GRC Access & On Security Role....................................................11
1.5 TRITON ACCESS................................................................................... 13
1.6 MS share point access..........................................................................18
2. Uploading documents in VSTF....................................................................18
3. Logging defect/bug for the failed test cases in VSTF..................................20
4. Upload Test plans in MTM...........................................................................22
5. Micro Soft Test Manager (MTM)..................................................................29
6. Accessibility standards...............................................................................34
7. CPM Tool..................................................................................................... 36
8. SAP landscape............................................................................................ 38
9. Roles and Responsibilities..........................................................................39
10. MS SAP COE Test Process......................................................................40
11. Area path and Iteration path guild lines..................................................40
12. Defect Guidelines.................................................................................... 41
12.1 Severity Definitions...............................................................................42
12.2 Priority Definitions................................................................................. 44

Introduction
This new joiner document helps newly on-boarded employees of Rio testing team
in obtaining the access and to get an over view of varies tool used in testing
process.
 Acquire Employee ID / v- Id

Join appropriate distribution lists/security groups

Install Visual Studio Team System -Team Suite

Install SAP GUI

Guide to install/Setup VSTF

Request access to systems as per the requirement:

Sandbox MSX and MPX

Dev MS1, MS2, MPD and MP2

Test MSG, MST, MST, MPG, MPT and MPU

Request access to file shares

Complete Security 101 Training within 5 days from onboarding and update

To get the On board mail, PMO team needs to be communicated.

1. Access Details
Access to various systems is documented in this section.

1.1 VSTF Installation

Click on Link: http://productsweb/settings.aspx

Click on search products

Enter the product name : Visual studio

 Version : 2012

Click on Search button

Click on visual studio 2012 team foundation server express PC x64

Double click on the item and select save settings button and select
language English- US

Click on install software button

Click on RUN button and install the VSTF in your system

To get access to VSTF RIO project, do the following

Request for VSTF access can be raised at the following link:

https://idweb/identitymanagement/default.aspx

Click on join a SG

Search for VSTF_OneEAS_Contributor

Select and click on Join. Next click on submit. An email will be sent
within 24 hours to confirm the VSTF access approval.
Once Access is provided do the following to connect to RIO project
in VSTF

Please follow the Steps to add new server SESIT in VSTF to track
FQR15 work items
 Open Visual Studio

Go to Team- Click on Connect to Foundation server

Click on Configure Team Projects

Click on Configure Team Projects

Search for Server msitvstf2

 Click on SESIT

Check box Click on Connect

1.2 MTM Access

Click on MTM Icon to Login to MTM

Select the project folder, Ex - Folder FY15 Q4 MQR click on Select

Plan
1.3 SAP GUI Log on pad installation

Click on Link: http://productsweb/settings.aspx

Click on search products

Enter the product name : SAP GUI

Version : 7.3

Click on Search button

 Double click on product

Click on install software button

Click on Run button and download it.

Run the file and click Install SAP Gui 7.30 under step 1.

After successful completion of step1 run the Step 2.

Finally run Run the SAP Gui Configuration Tool

 The below screen comes up

Select the option as show below

 Click on Update sap logon pad Configuration.

1.4 SAP GRC Access & On Security Role

SAP GRC request Procedure (For Production DO NOT raise access unless
approved by your Lead)
Please check with your POC to find out the list of systems for which the access
need to be raised. Below is the procedure to raise GRC requests MS1, MS2, MSU
and MST systems & Roles (sample).

Go to the link SAP Access.

You will get the screen as below. For the SAP Access click on Access
Requests/Model User.

Below is the screen you will find for Model User.

Make sure that the approver (Manager) name is correct.

Click on Next.
Give the model user as v-naveem (Confirm the model user to be entered
with the POCs. Depends on the systems for which the access is being
raised) and press enter key. You will get the following systems that you can
request the access for.
 Select the Landscapes required by consulting your supervisors and click
the arrow highlighted.

Click Next.

Change the Valid To: year from 9999 to a year ahead from the valid
date from.

Give the description as in the below screen shot: (Mention VSTF also
if possible).

Click on Next and check the details and submit the request.

1.5 TRITON ACCESS

Follow the below steps to get the access to triton file shares, if
required.

Click on the url : http://saprm/

Click on the Request New Access, click on Next.

 Select the Resource type(File Share) and the
sharepath(\\TRITON1\dev_transfer) and click on Next.

By default it shows current manager. Provide alternate manager if

required.

Ensure that the Manager is correct, if in doubt, please check with

Mentor or Lead.
 Select the radiobutton Read/Write and click on Next.

Click Next.
 Provide the description why you need access.

Click finish.
1.6 MS share point access

To obtain the access to MS Share point drop a note to the below people.
Anjani Vadlapudi- v-anvadl@microsoft.com

Raja Sekhar- v-ragaju@microsoft.com

2. Uploading documents in VSTF

Open VSTF link (web Based)

http://msitvstf2:8080/tfs/VSTFAT02/EAS_One

Search with Main VSTF number

Click on All links

 Double click on Test task

Click on attachments.
 Browse the file and give the comment and the click OK.

Once file is attached to the test VSTF, click on save to update the
changes.

After attaching save.

3. Logging defect/bug for the failed test cases in VSTF

 Search your work item in VSTF

Then go to WorkQueriesNewBug
 Enter the BUG Details and upload the Attachments

SAVE

BUG Number will be generated.

4. Upload Test plans in MTM

Click on test migrator plus and install

Binaries for
VS11Beta - TestCaseMigratorPlus(Excel-MHT) V1.2 RTM.zip

MTM Format:

MTM Format.xlsx
 Click on MTM Migrator plus

Click next
 Upload your test cases document under specify file path for excel
work book.

Click on next button.

Create new settings file and click on next

 Input all the required fields and then click next.

Select the respective Area path and Iteration path.

Deselect create area/iteration path from source values checkbox.

Click next.
 Deselect Create links between work items check box and click next.
 Select multiple test steps are present in single cell separated by
new line charter check box and click on next button.
 Click next

Click on save and migrate button

Wait until get the success message

 Click Start again to migrate other test cases or choose Close if
the migration is completed.

5. Micro Soft Test Manager (MTM)

 How to pass a test case in MTM?

Select your success test case>> Right click on the test case and
then pass it. So the test case will be marked as passed and will appear in
passed cases.

How to block the test case in MTM?

Select your blocked test case>>Right click on it and click block test,
then the test case will be marked as blocked.
 How to fail the test case in MTM?

Choose the failed test case>> Right click on the test case and then
click fail test, the test case will be marked as failed.

How to raise the bug from MTM?

Select the failed test case and click on Open test case on top or
double click on test case.
 The below screen comes up. Then click Create bug

Enter the defect details and attach the supporting document/test

evidence of the defect and then save it.
 Up on successful creation of bug a bug ID will get generated.
6. Accessibility standards.
We have to check the from address mail id, LOGO,
subject, BP number, invoice number, Dr Amount, Cr
Amount, Currency, payment type, Subscription
information and global billing details.
Check with business team for other languages are with
correct language.

Your credit has

been applied to your Microsoft Cloud Account.msg

For testing of accessibility standards

We have software for accessibility standard. We have to download the software.
We should not install the software. If you want to download we should have
access from Ramesh (V-RAMUTT).

Concept of accessibility standard:

As per US Government Rules and regulations Blind peoples they cant
read the mail. If we use this software they can listen the mail (what is
the mail, subject, and price information everything software can read)

Test Plan Format.

Test plan
format.xlsx

Test Evidence Format Document

Test evidence
format.docx
7. CPM Tool
After transport request review is complete, the transports have to
be released through CPT tool.

To release the task in CPM we have to add our id in owner list as

shown below
 To release a TR/CR, give the CR request in search field and search
for it.

Click Release SAP CR arrow will appear on the right side as shown
in the below screen shot, click on it.

The below screen appears.

 Sometime later refresh it and the below screen appears.

The TR is now moved to the other system.

8. SAP landscape

MS SAP landscape has ECC 6.0 running MS SAP core business processes.
9. Roles and Responsibilities

PM
Gather requirements from Business
Design solution, author Functional spec and conduct FS review
Unit testing in MS1
Configuration and documentation
Movement of TRs to MSU and maintaining TR list
Dev
Development of objects/work items in MS1
Adherence to coding standards / MS Best Practices
Unit testing in MS1
Creation and release of Dev item transport
Bug fixes
Test
Author test plan and conduct TP review
Adherence to MS Best Practices
 Preparation of test rationale
Testing carried out in MSG/MPG/MST/MPU
Raise functional issues and bugs
Documentation of testing results
Sending the test evidence for functionality owners for their review
and providing SIT sign off to in CPM.

10. MS SAP COE Test Process

11. Area path and Iteration path guild lines

The blow file paths will be used for different releases in FY 2016, the respective
area path and iteration path have to be used for testing.

FY16 Quarterly Release Iteration Paths:

EAS_One\FY16\M02 - Aug\QR
EAS_One\FY16\M05 - Nov\QR
EAS_One\FY16\M08 - Feb\QR
EAS_One\FY16\M11 - May\QR

FY16 Monthly Release Iteration Paths:

 EAS_One\FY16\M01 - Jul\Monthly
EAS_One\FY16\M03 - Sep\Monthly
EAS_One\FY16\M04 - Oct\Monthly
EAS_One\FY16\M06 - Dec\Monthly
EAS_One\FY16\M07 - Jan\Monthly
EAS_One\FY16\M09 - Mar\Monthly
EAS_One\FY16\M10 - Apr\Monthly
EAS_One\FY16\M12 - Jun\Monthly

FY16 OOC Iteration Paths:

EAS_One\FY16\M01 - Jul\OOC
EAS_One\FY16\M02 - Aug\OOC
EAS_One\FY16\M03 - Sep\OOC
EAS_One\FY16\M04 - Oct\OOC
EAS_One\FY16\M05 - Nov\OOC
EAS_One\FY16\M06 - Dec\OOC
EAS_One\FY16\M07 - Jan\OOC
EAS_One\FY16\M08 - Feb\OOC
EAS_One\FY16\M09 - Mar\OOC
EAS_One\FY16\M10 - Apr\OOC
EAS_One\FY16\M11 - May\OOC
EAS_One\FY16\M12 - Jun\OOC

The following subfolders will remain under QR, Monthly, and

OOC:
1 Initiate Delivery
2 Requirements
3 Design
4 Build
5 Stabilize SIT
6 Stabilize UAT
7 Deploy
8 Production

12. Defect Guidelines

During testing if the test is failed, tester has to raise a bug for the failed test
cases and attached the test evidence. While raising the bug, the below
guidelines are kept is mind and log the defect.

Field Details
Assigned To Select the name of the resource who
would be working on it
Priority 1 to 4
Area Auto picked by MTM
Iteration Auto picked by MTM
State Proposed
Active
Resolved
Severity 1 to 4
Reason New / Approved
Triaged Pending / Triaged
Root cause Choose the appropriate option
Repro Steps Steps to Reproduce
Symptom
System Info Environment details
History To provide further details, give your
comments.
Attachments Evidence document for the issue
Links Link Test case

12.1 Severity Definitions

Severity Definition Example

Severity 1 Defects resulting in: Online bugs that are severity 1

include:
Critical System unavailable
Server down , interface
System crash or unresponsive, or system
lockup significantly impaired
Unrecoverable data Scripting errors, Pages won't
corruption or loss render or Page closes down,
Inability to perform entered data is not saved or
core business incorrect data gets overwritten
functionality which Offline bugs that are severity 1
the application include:
supports, & impacts
many users. Crashes, hangs, Fatal assertion
failures or destroys files
Critical Privacy or
InfoSec violations, Causes serious data corruption
or violation of other or loss in some way
corporate policies.
Content or Documentation bugs that
No reasonable are severity 1 include:
workaround
Illegal terms or Public Relations
available
impact, or contain a virus
Violation of Microsoft Corporate
Polices, including Privacy,
Information Security or
Geopolitical reference, or
allowing unauthorized user
access.
Severity 2 Defects resulting in: Online bugs that are severity 2
include:
High System not
operating per Server or application
specification, but functionality noticeably
with less impact impaired but operates correctly
than Sev-1 issues or is not impacting large groups
(failure impacts few of users
users or in fails in
Obvious error in links or
non-typical user
navigation, or localization errors
scenarios)
Performance SLA not met , or
Significant
significant usability issues
performance or
response time issue Offline bugs that are severity 2
but operates include:
correctly
Non-fatal assertion failures or
High likelihood of Major functionality issues
data corruption or
loss Documentation bugs that are severity
2 include:
No reasonable
workaround Missing topics or TOC entries, or
available samples don't download
Highly visible broken links or
Editorial comments needing
removed

Severity 3 System not operating per Offline and Online bugs that are
specification with same as severity 3 include:
Medium
or less impact than Sev-2
Features not working completely
issues (key portions of
as specified, but core elements
feature works)
work
Low likelihood of
Documentation bugs that are severity
data corruption or
3 include:
loss
Major typographic or formatting
Clear workaround is
errors, incorrect
available
alphabetization/sorting
An individual sample which isn't
available or Less visible broken
links

Severity 4 System is working, but Offline, Online & Documentation bugs

with minor issues which that are severity 4 include:
Low
do not significantly
Trivial bugs or spelling
impede system
/grammar errors
functionality (slight
difference from spec) Incorrect screen or character
 Workaround may or sizing, or other cosmetic issues
may not available
Documentation bugs that are
severity 4 include:
Minor typographic and
formatting errors

12.2 Priority Definitions

Bug Priority Categories/Descriptions

Priority 1 High-Pri Production: Must resolve immediately in patch or hotfix,

or in the upcoming production release
(Must Fix)
Typically resolved within 1 day to 2 weeks
Only Pri 1 resolved out of planned release cycle
Must be fixed in pending production release
For some COEs, Pri 1 approved by Director or Sr.
Management
Is Critical to Business in order to avoid significant
business impact. Visible significant mis-spelling of
(Microsoft, etc) or contains illegal /offensive
terms
Dev/SIT/UAT: Must resolve immediately in patch or next
drop/build.
Easily reproducible and blocking further testing or
development work

Priority 2 Production: Must resolve in the next regular release

cycle deployment
Med-Pri
Pri 2 is never resolved out of planned release cycle
(Should Fix)
Not required to be fixed in current production
pending release, but must fix in next release.
Dev/SIT/UAT: Must resolve in next planned drop/build
before release to production
Has low risk of impacts from fix
Must fix before release from SIT to UAT, or from
UAT to production unless approved by Business.
Priority 3 Low-Pri Production and Dev/SIT/UAT: Will resolve if there are
time and resources available.
(Fix if Time)
Review to evaluate resolving in next planned
release cycle
Complex to reproduce. Non-Sev-1/Sev-2 defect
where the fix is not intuitively obvious or is a high-
risk fix, and should not be pursued until all higher
priority bugs are resolved