Life of Octad Software Product under Test

The lifecycle of a product starts once the business requirements are obtained from the client. The concerned team which is responsible for it will do a thorough analysis of the same and further design the technical specifications.

Business Testing end to End Interactions Actors & User Stories

Develop User Stories

1.Between Customer & Tradesmen

2.Between Customer & Admin

3.Between Tradesman & Admin

These specifications will help the technicians or developers to kick-start their job in software development. Steps involved here are explained below for your easy understanding. A user story is always informal and describe a user’s need. A use case can be either formal or informal, and describes system behavior. It is possible to have “tech” user stories, the same is not true for use cases. Once done, the user story is typically discarded

Step #1: Based on high-level product description, a software product is categorized into different modules and then into components or units. These units are developed independently so that their development can continue in parallel by engaging multiple developers.

Modules Involved From Back End

Customer & Tradesman Use Cases (Expected System Procedures)

tradesman Dashboard

PROFILE

Edit Profile

Edit Picture

Portfolio

Private Messages

PROJECTS

Latest Projects

Search Projects

My Bids

My Services

BILLING & FINANCE

Deposit Funds

Withdraw Funds

Escrow Payment

Transaction History

Manage Payments

My Subscriptions

Tasks Pending

News Feed

Dashboard

Profile

Projects

Finance

Buy Subscription

Subscription History

Deposit Funds

Withdraw Funds

Escrow Payment

Manage Payments

Transaction History

Latest Projects

Search Projects

My Bids

My Services

Services Sold

Admin Obfuscated

Once developed, these units are tested individually which will fall under Unit Testing.

Step #2: Individual validation ensures that all the units of a system are performing as expected on functional as well as feasibility grounds. These components, modules or sub-systems are integrated with the next level and then tested as an integrated unit in Integration testing.

Step #3: System Testing comes into the picture in this step where the integrated product would be tested first time as a whole in a pseudo-production environment. This level of testing is performed to check the compliance against functional as well as non-functional business requirements.

Step #4: It is a level of testing that is performed for client acceptability and hence, called as Acceptance Testing. This will be performed just before handling the software to the client, which is the Production

environment.

User Stories

Stage 1 of The Octad User Stories / End to End Testing will involve

Actors (any interaction from humans or the system that acts on our app )

Customer & Tradesman Interaction

Team 1 will Register as 5 Customers with Real Email Addresses & Phone Numbers

Team 2 will register as 5 Tradesmen also

Duration 1 Week

Digital Workbooks in Excel Will be supplied with use case preconditions and post conditions clearly showing the actors Scenarios and Goals of each Use Case also the stakeholders in case of a bug or aesthetic improvements (PROMPTS for more use cases or users or ….) and other amendments expected or suggested by the TESTER

FeedBack must be Detailed online With Bugs on OS Devices Assigned for Use Reminder What is a user story in Agile development?

User stories are one of the primary development artifacts for Scrum and Extreme Programming (XP) project teams. A user story is a very high-level definition of a requirement, containing just enough information so that the developers can produce a reasonable estimate of the effort to implement it