SlideShare a Scribd company logo
1 of 12
Dev box testing
By Mithilesh Singh
What?
• Dev Box is an abridged version of ‘Developer Machine’.In Dev
Box testing, a qualityengineer validates,tests, and verifies a
feature in scope on the developer’smachine. It’s as simple as
that. A basic approach through which one ensures the quality
of a feature.
How?
• The process of successful Dev Box testing starts early
in the development cycle, when the feature is being
discussed between the Product, Dev, and QA teams.
While a story is being groomed, a quality engineer
ensures the following are in place:
• Acceptance criteria.
• In scope and out of scope features.
• Pre-conditions, if any
• Once the above parameters are concluded, the dev
team can start working on it. After the development
is finished, the SDE will call out for dev box testing.
Steps:
• The qualityengineer reviews the story and checks the preconditions.
• Ask the developerto show the workflow to ensure the required
functionalityis working
• Review the unit, functional,integrationtests and execute them.
• Ask questions to the developer
- When would this fail in production? What wouldbe possible
scenarios?
- Would this perform as expected under performance-stress-load
tests?
- Are there any known issues with the code, module, or integrations?
- What edge cases havethey handledin the implementation?
- Is there a better way to implement the same code?
- Are there any platform or hardware constraints?
- Questions around scenarios of localization,etc.
Note:
The questions would depend on what type of story
you’re testing, for example: front-end or back-end
stories.
While going through the above points, note the
details such as discussion points, issues found,
suggested changes, action items, and share them as
minutes of meeting.
This would ensure the required updates are made. If
no issues are found, the developer can then merge
the code to the staging branch where the quality
engineer would execute functional tests.
Benefits?
Technical understanding of the
product by the quality engineer
Upskilling quality engineer
provides faster feedback to the
team
Improve vertical testing
Improve cross-team
communication and build trust
Drawbacks?
It may take time to get each team member in sync
If the team is not following the TDD approach, it may prove difficult or futile
The team should consist of at least two quality engineers (Dev Box is quality-
centric,hence, wouldrequireenoughQEs to accommodateall tasks)
End to End
Testing
Steps
The teamwill be there in the sprint backlog groomingmeetingand decide the Stories
that are all can pick in the upcomingsprint.
Dev and Tester will be in sync duringScope analysis and theywill divide the feature
into testable components.
The developer will be creatingthe Jira task based on those testable
components[backend and front end development tasks].
Testers will be addingall those testable components in the Google sheet with sprint
and JIRA task details.he/shill will also mention ETA for every task/subtask for their
reference.
The designer will share the Figma for that feature and that will be the road map for
the testers and developer for further activity.
The developer will be developingthe feature as per the timeline mentionedin the
google sheet and the tester meanwhile writingthe test cases for that feature.
End to End
Testing
Steps
Note: Tester can draft all the cases at once no matter which component is going
to come first for the testing but make sure test case writing is done before
receiving any build.
Once the developer developed the component he/she can call tester for dev box
testing, testers can follow slide 4 and 5 to perform the dev box testing.
After dev box Build will be pushed to the respective env--> netlify or staging.
The tester should verify Test environment details [Testing portal link, test data,
.apk, release notes, dependent areas list, bug fixes list, JIRA ticket etc.]before
starting the test execution.
The tester will start testing the component based on the written test case and
update the test case status in the test case sheet.
If Testers encounter any bug, he/she will report it to the respective dev and add
the JIRA in front of the test case.
End to End Testing Steps
This development and testing process
with bug life cycle will be continued
and after executing all the cases we
will have execution results for all
the cases.
There are possibilities to get
some Adhoc requests in between for
the same developing components or
some already developed feature also.
if there is some enhancement needed
in between in currentfeature, the
developer has to convey their QA
regardingthis so that he/she can
modify test cases accordingly and till
the time those changes will reflect
tester will have a case ready
for testing
• Older feature Adhoc request: if this is on priority and we cannot put on hold, Analyse and decide whether it is non-
functionalchanges like UI/UX or functionalchanges. for UI/UX changes we can skip test case writing and direct update
the JIRA ticket based on activity performed but if there are functionalchanges try to add the test case first, that kind of
changes will not containmore cases so will hardlytake 30-40 mins time to draft/modify the cases.
End to End Testing Steps
01
Note: dev box testing will help to
avoid major bugs in staging or
pre prod and dev will have
enough time to fix it if any
02
Once Developmentand testing
are done, the tester will add the
deliverables in test plan
with documentslike test
case sheet, execution status etc.
03
In the test plan, the only tester
can mark the sign off date and
status and share with the dev
and team lead.
Note: Tester who does not follow
or not aware the Dev box testing
can directly perform deep testing
on staging or preprod but dev
might get less time to fix logged
bugs and sprint will get delayed.
Dev box testing.pdf

More Related Content

Similar to Dev box testing.pdf

Acceptance test driven development
Acceptance test driven developmentAcceptance test driven development
Acceptance test driven development
Editor Jacotech
 
Aim (A).pptx
Aim (A).pptxAim (A).pptx
Aim (A).pptx
14941
 
Manual testing real time questions by subbu
Manual testing real time questions by subbuManual testing real time questions by subbu
Manual testing real time questions by subbu
palla subrahmanyam
 

Similar to Dev box testing.pdf (20)

www.tutorialsbook.com presents Manual testing
www.tutorialsbook.com presents Manual testingwww.tutorialsbook.com presents Manual testing
www.tutorialsbook.com presents Manual testing
 
Introduction to testing.
Introduction to testing.Introduction to testing.
Introduction to testing.
 
Automation Testing Project and Framework Details
Automation Testing Project and Framework DetailsAutomation Testing Project and Framework Details
Automation Testing Project and Framework Details
 
manual-testing
manual-testingmanual-testing
manual-testing
 
Qa interview questions and answers for placements
Qa interview questions and answers for placementsQa interview questions and answers for placements
Qa interview questions and answers for placements
 
Stlc 12 Steps Ppt
Stlc 12 Steps PptStlc 12 Steps Ppt
Stlc 12 Steps Ppt
 
How to overcome agile methodology challenges
How to overcome agile methodology challengesHow to overcome agile methodology challenges
How to overcome agile methodology challenges
 
Scrum Process Overview
Scrum Process OverviewScrum Process Overview
Scrum Process Overview
 
Acceptance test driven development
Acceptance test driven developmentAcceptance test driven development
Acceptance test driven development
 
Aim (A).pptx
Aim (A).pptxAim (A).pptx
Aim (A).pptx
 
Qa interview questions and answers
Qa interview questions and answersQa interview questions and answers
Qa interview questions and answers
 
Quality assurance by Sadquain
Quality assurance by Sadquain Quality assurance by Sadquain
Quality assurance by Sadquain
 
Manual testing real time questions by subbu
Manual testing real time questions by subbuManual testing real time questions by subbu
Manual testing real time questions by subbu
 
Project Management in 3 Slides
Project Management in 3 SlidesProject Management in 3 Slides
Project Management in 3 Slides
 
General technical interview questions
General technical interview questionsGeneral technical interview questions
General technical interview questions
 
stlc
stlcstlc
stlc
 
Software Testing
Software TestingSoftware Testing
Software Testing
 
All about testing
All about testingAll about testing
All about testing
 
Quality Assurance Process
Quality Assurance ProcessQuality Assurance Process
Quality Assurance Process
 
Development and test infrastructure
Development and test infrastructureDevelopment and test infrastructure
Development and test infrastructure
 

More from Mithilesh Singh

More from Mithilesh Singh (20)

Cucumber Basics.pdf
Cucumber Basics.pdfCucumber Basics.pdf
Cucumber Basics.pdf
 
Data Migration.pdf
Data Migration.pdfData Migration.pdf
Data Migration.pdf
 
SDLC Models.pdf
SDLC Models.pdfSDLC Models.pdf
SDLC Models.pdf
 
Test_Case_Design_Techniques
Test_Case_Design_TechniquesTest_Case_Design_Techniques
Test_Case_Design_Techniques
 
Performance Testing
Performance TestingPerformance Testing
Performance Testing
 
Software_requirement_collection
Software_requirement_collectionSoftware_requirement_collection
Software_requirement_collection
 
Stub_&_Drive
Stub_&_DriveStub_&_Drive
Stub_&_Drive
 
TestersMindSet 2022
TestersMindSet 2022TestersMindSet 2022
TestersMindSet 2022
 
API_Testing_with_Postman
API_Testing_with_PostmanAPI_Testing_with_Postman
API_Testing_with_Postman
 
Agile_basics
Agile_basicsAgile_basics
Agile_basics
 
Selenium_Grid
Selenium_GridSelenium_Grid
Selenium_Grid
 
Appium_set_up
Appium_set_upAppium_set_up
Appium_set_up
 
Appium- part 1
Appium- part 1Appium- part 1
Appium- part 1
 
Alpha & Beta Testing
Alpha & Beta TestingAlpha & Beta Testing
Alpha & Beta Testing
 
Severity and Priority
Severity and PrioritySeverity and Priority
Severity and Priority
 
GIT_Overview.
GIT_Overview.GIT_Overview.
GIT_Overview.
 
Selenium-Locators
Selenium-LocatorsSelenium-Locators
Selenium-Locators
 
Browser_Stack_Intro
Browser_Stack_IntroBrowser_Stack_Intro
Browser_Stack_Intro
 
UI_UX_testing tips
UI_UX_testing tipsUI_UX_testing tips
UI_UX_testing tips
 
Emulator vs Simulator
Emulator vs SimulatorEmulator vs Simulator
Emulator vs Simulator
 

Recently uploaded

Recently uploaded (20)

A Deep Dive into Secure Product Development Frameworks.pdf
A Deep Dive into Secure Product Development Frameworks.pdfA Deep Dive into Secure Product Development Frameworks.pdf
A Deep Dive into Secure Product Development Frameworks.pdf
 
Navigation in flutter – how to add stack, tab, and drawer navigators to your ...
Navigation in flutter – how to add stack, tab, and drawer navigators to your ...Navigation in flutter – how to add stack, tab, and drawer navigators to your ...
Navigation in flutter – how to add stack, tab, and drawer navigators to your ...
 
The Strategic Impact of Buying vs Building in Test Automation
The Strategic Impact of Buying vs Building in Test AutomationThe Strategic Impact of Buying vs Building in Test Automation
The Strategic Impact of Buying vs Building in Test Automation
 
Novo Nordisk: When Knowledge Graphs meet LLMs
Novo Nordisk: When Knowledge Graphs meet LLMsNovo Nordisk: When Knowledge Graphs meet LLMs
Novo Nordisk: When Knowledge Graphs meet LLMs
 
Your Ultimate Web Studio for Streaming Anywhere | Evmux
Your Ultimate Web Studio for Streaming Anywhere | EvmuxYour Ultimate Web Studio for Streaming Anywhere | Evmux
Your Ultimate Web Studio for Streaming Anywhere | Evmux
 
UNI DI NAPOLI FEDERICO II - Il ruolo dei grafi nell'AI Conversazionale Ibrida
UNI DI NAPOLI FEDERICO II - Il ruolo dei grafi nell'AI Conversazionale IbridaUNI DI NAPOLI FEDERICO II - Il ruolo dei grafi nell'AI Conversazionale Ibrida
UNI DI NAPOLI FEDERICO II - Il ruolo dei grafi nell'AI Conversazionale Ibrida
 
From Knowledge Graphs via Lego Bricks to scientific conversations.pptx
From Knowledge Graphs via Lego Bricks to scientific conversations.pptxFrom Knowledge Graphs via Lego Bricks to scientific conversations.pptx
From Knowledge Graphs via Lego Bricks to scientific conversations.pptx
 
Test Automation Design Patterns_ A Comprehensive Guide.pdf
Test Automation Design Patterns_ A Comprehensive Guide.pdfTest Automation Design Patterns_ A Comprehensive Guide.pdf
Test Automation Design Patterns_ A Comprehensive Guide.pdf
 
Abortion Clinic In Pretoria ](+27832195400*)[ 🏥 Safe Abortion Pills in Pretor...
Abortion Clinic In Pretoria ](+27832195400*)[ 🏥 Safe Abortion Pills in Pretor...Abortion Clinic In Pretoria ](+27832195400*)[ 🏥 Safe Abortion Pills in Pretor...
Abortion Clinic In Pretoria ](+27832195400*)[ 🏥 Safe Abortion Pills in Pretor...
 
Prompt Engineering - an Art, a Science, or your next Job Title?
Prompt Engineering - an Art, a Science, or your next Job Title?Prompt Engineering - an Art, a Science, or your next Job Title?
Prompt Engineering - an Art, a Science, or your next Job Title?
 
Microsoft365_Dev_Security_2024_05_16.pdf
Microsoft365_Dev_Security_2024_05_16.pdfMicrosoft365_Dev_Security_2024_05_16.pdf
Microsoft365_Dev_Security_2024_05_16.pdf
 
From Theory to Practice: Utilizing SpiraPlan's REST API
From Theory to Practice: Utilizing SpiraPlan's REST APIFrom Theory to Practice: Utilizing SpiraPlan's REST API
From Theory to Practice: Utilizing SpiraPlan's REST API
 
Weeding your micro service landscape.pdf
Weeding your micro service landscape.pdfWeeding your micro service landscape.pdf
Weeding your micro service landscape.pdf
 
Wired_2.0_CREATE YOUR ULTIMATE LEARNING ENVIRONMENT_JCON_16052024
Wired_2.0_CREATE YOUR ULTIMATE LEARNING ENVIRONMENT_JCON_16052024Wired_2.0_CREATE YOUR ULTIMATE LEARNING ENVIRONMENT_JCON_16052024
Wired_2.0_CREATE YOUR ULTIMATE LEARNING ENVIRONMENT_JCON_16052024
 
Workshop - Architecting Innovative Graph Applications- GraphSummit Milan
Workshop -  Architecting Innovative Graph Applications- GraphSummit MilanWorkshop -  Architecting Innovative Graph Applications- GraphSummit Milan
Workshop - Architecting Innovative Graph Applications- GraphSummit Milan
 
Spring into AI presented by Dan Vega 5/14
Spring into AI presented by Dan Vega 5/14Spring into AI presented by Dan Vega 5/14
Spring into AI presented by Dan Vega 5/14
 
Encryption Recap: A Refresher on Key Concepts
Encryption Recap: A Refresher on Key ConceptsEncryption Recap: A Refresher on Key Concepts
Encryption Recap: A Refresher on Key Concepts
 
OpenChain Webinar: AboutCode and Beyond - End-to-End SCA
OpenChain Webinar: AboutCode and Beyond - End-to-End SCAOpenChain Webinar: AboutCode and Beyond - End-to-End SCA
OpenChain Webinar: AboutCode and Beyond - End-to-End SCA
 
Rapidoform for Modern Form Building and Insights
Rapidoform for Modern Form Building and InsightsRapidoform for Modern Form Building and Insights
Rapidoform for Modern Form Building and Insights
 
Abortion Pill Prices Turfloop ](+27832195400*)[ 🏥 Women's Abortion Clinic in ...
Abortion Pill Prices Turfloop ](+27832195400*)[ 🏥 Women's Abortion Clinic in ...Abortion Pill Prices Turfloop ](+27832195400*)[ 🏥 Women's Abortion Clinic in ...
Abortion Pill Prices Turfloop ](+27832195400*)[ 🏥 Women's Abortion Clinic in ...
 

Dev box testing.pdf

  • 1. Dev box testing By Mithilesh Singh
  • 2. What? • Dev Box is an abridged version of ‘Developer Machine’.In Dev Box testing, a qualityengineer validates,tests, and verifies a feature in scope on the developer’smachine. It’s as simple as that. A basic approach through which one ensures the quality of a feature.
  • 3. How? • The process of successful Dev Box testing starts early in the development cycle, when the feature is being discussed between the Product, Dev, and QA teams. While a story is being groomed, a quality engineer ensures the following are in place: • Acceptance criteria. • In scope and out of scope features. • Pre-conditions, if any • Once the above parameters are concluded, the dev team can start working on it. After the development is finished, the SDE will call out for dev box testing.
  • 4. Steps: • The qualityengineer reviews the story and checks the preconditions. • Ask the developerto show the workflow to ensure the required functionalityis working • Review the unit, functional,integrationtests and execute them. • Ask questions to the developer - When would this fail in production? What wouldbe possible scenarios? - Would this perform as expected under performance-stress-load tests? - Are there any known issues with the code, module, or integrations? - What edge cases havethey handledin the implementation? - Is there a better way to implement the same code? - Are there any platform or hardware constraints? - Questions around scenarios of localization,etc.
  • 5. Note: The questions would depend on what type of story you’re testing, for example: front-end or back-end stories. While going through the above points, note the details such as discussion points, issues found, suggested changes, action items, and share them as minutes of meeting. This would ensure the required updates are made. If no issues are found, the developer can then merge the code to the staging branch where the quality engineer would execute functional tests.
  • 6. Benefits? Technical understanding of the product by the quality engineer Upskilling quality engineer provides faster feedback to the team Improve vertical testing Improve cross-team communication and build trust
  • 7. Drawbacks? It may take time to get each team member in sync If the team is not following the TDD approach, it may prove difficult or futile The team should consist of at least two quality engineers (Dev Box is quality- centric,hence, wouldrequireenoughQEs to accommodateall tasks)
  • 8. End to End Testing Steps The teamwill be there in the sprint backlog groomingmeetingand decide the Stories that are all can pick in the upcomingsprint. Dev and Tester will be in sync duringScope analysis and theywill divide the feature into testable components. The developer will be creatingthe Jira task based on those testable components[backend and front end development tasks]. Testers will be addingall those testable components in the Google sheet with sprint and JIRA task details.he/shill will also mention ETA for every task/subtask for their reference. The designer will share the Figma for that feature and that will be the road map for the testers and developer for further activity. The developer will be developingthe feature as per the timeline mentionedin the google sheet and the tester meanwhile writingthe test cases for that feature.
  • 9. End to End Testing Steps Note: Tester can draft all the cases at once no matter which component is going to come first for the testing but make sure test case writing is done before receiving any build. Once the developer developed the component he/she can call tester for dev box testing, testers can follow slide 4 and 5 to perform the dev box testing. After dev box Build will be pushed to the respective env--> netlify or staging. The tester should verify Test environment details [Testing portal link, test data, .apk, release notes, dependent areas list, bug fixes list, JIRA ticket etc.]before starting the test execution. The tester will start testing the component based on the written test case and update the test case status in the test case sheet. If Testers encounter any bug, he/she will report it to the respective dev and add the JIRA in front of the test case.
  • 10. End to End Testing Steps This development and testing process with bug life cycle will be continued and after executing all the cases we will have execution results for all the cases. There are possibilities to get some Adhoc requests in between for the same developing components or some already developed feature also. if there is some enhancement needed in between in currentfeature, the developer has to convey their QA regardingthis so that he/she can modify test cases accordingly and till the time those changes will reflect tester will have a case ready for testing • Older feature Adhoc request: if this is on priority and we cannot put on hold, Analyse and decide whether it is non- functionalchanges like UI/UX or functionalchanges. for UI/UX changes we can skip test case writing and direct update the JIRA ticket based on activity performed but if there are functionalchanges try to add the test case first, that kind of changes will not containmore cases so will hardlytake 30-40 mins time to draft/modify the cases.
  • 11. End to End Testing Steps 01 Note: dev box testing will help to avoid major bugs in staging or pre prod and dev will have enough time to fix it if any 02 Once Developmentand testing are done, the tester will add the deliverables in test plan with documentslike test case sheet, execution status etc. 03 In the test plan, the only tester can mark the sign off date and status and share with the dev and team lead. Note: Tester who does not follow or not aware the Dev box testing can directly perform deep testing on staging or preprod but dev might get less time to fix logged bugs and sprint will get delayed.