Scribd
Upload
45 views

Manual Tesing Document

The document discusses an agenda for a Salesforce testing training. It covers topics like why testing is needed, the Salesforce testing lifecycle, Salesforce terminology, testing methodologies like Agile and Scrum, and roles in testing. Key Salesforce concepts like Epics, User Stories, and Tasks are also defined.

Uploaded by

anveshini.testing
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
45 views

Manual Tesing Document

The document discusses an agenda for a Salesforce testing training. It covers topics like why testing is needed, the Salesforce testing lifecycle, Salesforce terminology, testing methodologies like Agile and Scrum, and roles in testing. Key Salesforce concepts like Epics, User Stories, and Tasks are also defined.

Uploaded by

anveshini.testing
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 24

Agenda

• Why Software Testing


• What is STLC
• Why Salesforce Testing
• Salesforce Key terminologies
• Salesforce Testing Process
• Project Methodologies(Agile)
• JIRA Tool/ Management Tool
• Salesforce Testing Strategy
• Roles and Responsibilities of a Tester
• Interview Tips
• Any questions ?
Why Testing is Needed
3
4
5
6
7
8
9
10
11
How is Agile different from Scrum?
The key difference between Agile and Scrum is that Agile is a philosophy about how to
successfully deliver software to a customer, while Scrum is a proven methodology for
software development teams to follow.
Agile means “incremental, allowing teams to develop projects in small increments. Scrum is
one of the many types of agile methodology, known for breaking projects down into sizable
chunks called “sprints.” Agile scrum methodology is good for businesses that need to finish
specific projects quickly.

12
13
14
15
16
17
18
19
Epic
An Epic is useful as placeholders for large requirements. It probably won’t fit into a sprint and should be
broken down into stories. Epics are usually defined during the initial product roadmap and decomposed
into stories in the product backlog as more is learned and is usually written in a User Story format.

User Stories
User stories are the smallest units of user functionality in agile which can be delivered in one agile sprint.
They are typically estimated using story pointed and defined using INVEST criteria.

Tasks
Tasks are decomposed parts of a story that get into HOW the story will be completed. Tasks can be hour
estimated if desired. Tasks are usually defined by the people doing the work (developers, QA, etc),
whereas stories and epics are generally created by the customer or the product owner on behalf of the
customer. Thus, the tasks no longer need to be understandable by business users and so can be highly
technical. The process of breaking a story down into tasks also helps the development team better
understand what needs to be done.

20
21
22
23
Burn down and burn up charts are two types of charts that project managers use to track
and communicate the progress of their projects. A burn down chart shows how much work
is remaining to be done in the project, whereas a burn up shows how much work has been
completed, and the total amount of work.

24

You might also like