Code workshop
Download as PPTX, PDF0 likes279 views
This document summarizes a half day workshop on user stories and transitioning a project. It includes an agenda with topics on user stories, creating transition tickets, developing database layers and forms, and testing. Presenters include Syed Mansoor Ahmed and Ankit Kashyap from Wipro. The workshop covers writing user stories and SQL stored procedures, making corresponding database methods, and building the UI with controls and wiring up data. It emphasizes testing, documentation, and following best practices for validation, source control, and other aspects.
Code workshop
- 2. Syed Mansoor Ahmed (Project Manager) Proud Wiproite from last 10 Yrs Leads AppC Automation team syedmansoor.ahamed@wipro.com Ankit Kashyap (Analyst Programmer) Proud Wiproite from last 5.9 Yrs Developer for AppC tools ankit.kashyap@wipro.com
- 5. http://en.wikipedia.org/wiki/User_story • A user story is one or more sentences in the everyday or business language of the end user or user of a system that captures what a user does or needs to do as part of his or her job function. • Basis for defining the functions a business system must provide, and to facilitate requirements management. • It captures the 'who', 'what' and 'why' of a requirement in a simple, concise way, often limited in detail by what can be hand-written on a small paper notecard. • User stories are written by or for the business user as that user's primary way to influence the functionality of the system being developed. User stories may also be written by developers to express non-functional requirements (security, performance, quality, etc.)
- 6. • "As a <role>, I want <goal/desire> so that <benefit>" • "As a <role>, I want <goal/desire>" • "In order to <receive benefit> as a <role>, I want <goal/desire>" • "As <who> <when> <where>, I <what> because <why>."
- 7. • As a user, I want to search for my customers by their first and last names. • As a non-administrative user, I want to modify my own schedules but no the schedules of other users. • As a mobile application tester, I want to test my test cases and report results to my management.
- 10. And Put some dummy data
- 12. • What are the required fields for creating a Transition Tkt? • Make a Sproc – Test it! • Make a Corresponding method in DB Layer • Now, make form • On submit button, fetch data from UI and pass to the DB Layer!
- 14. • What we need to show on UI? • Write a Sproc – Test it! • Make a Corresponding method in DB Layer • In Page Load method, fill the GridView with the data
- 15. • What we need to show on UI? • Write a Sproc – Test it! • Make a Corresponding method in DB Layer • In Page Load method, fill the GridView with the data
- 16. • What we need to show on UI? • Write a Sproc – Test it! • Make a Corresponding method in DB Layer • Make UI with controls • In Page Load method, wire up data with controls
- 17. • What we need to show on UI? • Write a Sproc – Test it! (Can we use View page’s Sproc) • Make a Corresponding method in DB Layer for initial Data • Make UI with controls • In Page Load method, wire up data with controls • On Submit, update database with each question status Look and feel of Update page should be same as View Page
- 18. • My/All Page with Completion % • Place Edit/View Links in “My” and “All” Pages. • Place Edit button on View Page. • Time for Validation!!!!
- 19. Unit Tests Source version control Documentation – SRS? User manual? Client Side validation CSS Logos/Access control Provision for adding new Questions