Team Leads/Experts

Anju Kurup
Fasiullah(Drivers Pay)

Shraddha Agrawal PQL

Shreya Joshi
Rishi Khandelwal CAST/CART advocate

Ruchita Bhatane
Naveen
Gaurav Gawade

Phanidranath Orrugant

Swetank Rupesh Kumar

Debabrata Pal

Gaurav Agarwal
Falguni/Arun (Love Shares)
Neha Patl

Rajani Nelluri

Kalpana Timmapuram
Sradhanjali Khadanga

A, Kaarthik
John Kenady Madda
Aart Parab
 Shreya Joshi Phanidranath Orrugant

Fasiullah Naveen

Rupesh Kumar Falguni Dedhia

Phanidranath Orrugant Debabrata Pal

 Guidelines
• Team leads :
– REVIEWS (TSD/TUT/DEG) & Code (CDR)
– Testng
– Resolve Bottle Necks
– Issue log – review/upload & send me the link.
• Aart & John to test the scenarios & provide data. (Objects have to be
evenly distributed)
• After confirmaton from each level the code will be delivered to
Onsite.
• Swetank reviews/test after confirmaton from Aart/John & Team
leads.
• Code should be checked for ATC, SLIN, CI, & CART
• Code should follow naming conventons
 Guidelines…
• TUT scenarios should be verified against FSD
• Swetank or Sarah should be involved in meetngs with Onsite
functonal team
• Any issue or bottlenecks should be first addressed to team
leads/experts.
• Any delays in object deliveries should have a valid & strong
justficatons.
• Follow-up on issue logs should be promptly done by
developers.
• Request for test data should be done in advance & not when
you start testng.
 Guidelines…
• No assumptons should be made during
development, clarify everything & follow FSD.
• FSD reviews with functonal team member
should be conducted before development
starts.
• During these FSD reviews, test case scenarios
should be discussed and added to the SSD for
cases when the SSD does not have detailed test
case scenarios.
 Guidelines…
• FUT or defects raised by onsite has to follow process (will be
explained)
• Incorporate only valid fixes & minor changes.
• Any functonality change should be immediately
communicated to Swetank and Sarah (for change request)
• Any change which can take more then 2-3 hours should be
immediately communicated to Swetank and Sarah
• Retest SHOULD be done for all scenarios after FUT fixes.
• TUT document should be updated during retests.
• TUT document should reflect the most recent testng results