Developer Tea exists to help driven developers connect to their ultimate purpose and excel at their work so that they can positively impact the people they influence. With over 13 million downloads to date, Developer Tea is a short podcast hosted by Jonathan Cutrell (@jcutrell), co-founder of Spec and Director of Engineering at PBS. We hope you'll take the topics from this podcast and continue the conversation, either online or in person with your peers. Twitter: @developertea :: Email: deve ...
…
continue reading
Content provided by Dustin Reybrouck: IT System Administrator. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Dustin Reybrouck: IT System Administrator or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!
Go offline with the Player FM app!
SAS 006 – Testing 123
MP3•Episode home
Manage episode 219678819 series 1751234
Content provided by Dustin Reybrouck: IT System Administrator. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Dustin Reybrouck: IT System Administrator or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Today’s Show: Testing 123
- Developing good testing practices is important
- Computer hardware/software testing
- Backup restore testing
- Documentation & process testing
- Patch testing
- OS
- Application
- The basics
- Pre-test, validate current state
- What works, what doesn’t
- Partner with business community if needed
- Build test environment
- Useful for more complicated or critical systems
- Virtualization has made this easy
- Pre-test the development environment, does it match production?
- Take notes on the steps you take, so you know what to expect during the production upgrade
- Verify backups
- Have a fail back plan
- Outline situations when it would be needed
- Post-testing
- Does system functionality match the pre-test?
- Use acceptance test required?
- Pre-test, validate current state
- Testing process
- Be as thorough as time allows based on upgrade scope and system importance
- How much time & money will an outage cost you?
- Don’t assume anything
- Even the smallest detail can have a significant effect on the outcome
- How many people are required?
- What equipment is required?
- Phones
- Printers
- Computers/Servers
- Time required?
- Be as thorough as time allows based on upgrade scope and system importance
Final Thoughts
- Good testing habits will save you time, money and embarrassment
- Resist the urge to just get it done
- It’s better to do it right then to get home 10 minutes earlier. Otherwise you might be driving back into work to fix it.
- Testing decreases this temptation because you can use your notes as a checklist
56 episodes
MP3•Episode home
Manage episode 219678819 series 1751234
Content provided by Dustin Reybrouck: IT System Administrator. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Dustin Reybrouck: IT System Administrator or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Today’s Show: Testing 123
- Developing good testing practices is important
- Computer hardware/software testing
- Backup restore testing
- Documentation & process testing
- Patch testing
- OS
- Application
- The basics
- Pre-test, validate current state
- What works, what doesn’t
- Partner with business community if needed
- Build test environment
- Useful for more complicated or critical systems
- Virtualization has made this easy
- Pre-test the development environment, does it match production?
- Take notes on the steps you take, so you know what to expect during the production upgrade
- Verify backups
- Have a fail back plan
- Outline situations when it would be needed
- Post-testing
- Does system functionality match the pre-test?
- Use acceptance test required?
- Pre-test, validate current state
- Testing process
- Be as thorough as time allows based on upgrade scope and system importance
- How much time & money will an outage cost you?
- Don’t assume anything
- Even the smallest detail can have a significant effect on the outcome
- How many people are required?
- What equipment is required?
- Phones
- Printers
- Computers/Servers
- Time required?
- Be as thorough as time allows based on upgrade scope and system importance
Final Thoughts
- Good testing habits will save you time, money and embarrassment
- Resist the urge to just get it done
- It’s better to do it right then to get home 10 minutes earlier. Otherwise you might be driving back into work to fix it.
- Testing decreases this temptation because you can use your notes as a checklist
56 episodes
All episodes
×Welcome to Player FM!
Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.