Scribd
Upload
2 views4 pages

Software Development Testing Workflow

The document outlines a detailed task module for a software development project, including various phases such as requirement gathering, testing, and client feedback incorporation. Each task is associated with estimated effort in hours and status updates, indicating which tasks are completed, in progress, or not started. The timeline includes key dates for releases and reviews, culminating in a client release scheduled for October 29th.

Uploaded by

Aashu Jain
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
2 views4 pages

Software Development Testing Workflow

The document outlines a detailed task module for a software development project, including various phases such as requirement gathering, testing, and client feedback incorporation. Each task is associated with estimated effort in hours and status updates, indicating which tasks are completed, in progress, or not started. The timeline includes key dates for releases and reviews, culminating in a client release scheduled for October 29th.

Uploaded by

Aashu Jain
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd

Task Module Effort(in Depende

# hrs) ncy
1 Requirement gathering
2 FRS/Functional flow doc preparation
3 HLTC preparation and send to BA for review

4 HLTC BA review and send feedback to QA


5 LLTC preparation and send to BA for review
6 LLTC BA review and send feedback to QA
9 Unit Testing after development (For 19/Sep release) 2

10 Demo to BA by Dev Team (for internal Sep release) 2

11 BA review on Dev completed tasks (06/Sep Tasks)

11.1 BA review on Dev completed tasks (24/Sep Tasks) 2


a
11.1 BA review on Dev completed tasks (19/Sep Release)

12 BA Feedback and HLTC execution by Dev. Team before QA release

13 Release to QA for 1st Round of Testing (Internal Release testing)

14 1st Round Testing of the application


15 Bug Fixing and Release to QA for Retesting 24
16 2nd Round Testing (Official Release to client- TBP) - 27/Sep Release

17 Unit testing Parallelly bug fixing & deployment for client demo 8 API

18 Unit testing Parallelly bug fixing & deployment for client demo 8 Watch
App
19 Client Feedback incorporated by Dev team and send release to QA

20 Build shared for BA/UI-UX Review iOS and Android

21 BA Feedbacks on BUild Review


UI/UX Feedbacks on BUild Review
22 Bug Fixing and Release to QA for Retesting
25 Demo 2 to Client
27 QA Rel with all features developed till 14/Oct

27.1 Bug fixes on QA feedbacks and CLinet feedbacks(ifany)

27.2 QA rel with all bug fixes and client demo feedbacks if any
28 Client release - with all featires developeed and QA bug fixes till
29/Oct

29 Retesting and ad-hoc testing of the Companion app

29.1 Bug fixes on QA feedbacks

29.2 QA rel with all bug fixes and client demo feedbacks if any

30 Firmware rel updates with all developed features

31 Sanity testing on updated Firmware sent by ODM

32 Final Testing of the app and signoff

33 IOS Release to QA with HLTC Execution

34 QA completion - iOS Release

35 Android Release to QA with HLTC Execution


36 QA completion - Android Release
Dev Start Dev End Status Status Resource Remarks

Done
Done
Done

Done
Done
Done
Done

Done

Done

Done

Done

Done

Done

Done
Done
Done

Done

Done

Done

Done

Done
Done
Done
Done
Done

In
progress
In
progress
Done 04/Nov: VM: CLient
release done and
awaiting his
feedbacks.
22/Oct:VM:
Tentatively planning
for 30/Oct

In 04/Nov: Vm: New


progress tasks added for the
pending features
testing on the build
for Client rel done
on 30/Oct.

Not
Started

Not
Started
In 16/Dec: VM:
progress Delayed reason -
Existing tasks
Not
Started
Done
In
progress

You might also like