Mastering Postman: Organizing Tests for Success with Kristin Jackvony
summary
Postman workspace and collection management advice for reliable API testing: use clear naming and capitalization, keep environments short and CAPITALIZE ENV NAMES so dropdowns are readable, treat variables as case sensitive and avoid abbreviations, and star frequently used collections. Place assertions at collection/folder/request depending on scope (headers or response-time at collection, folder-wide codes or bodies at folder, unique checks at request). Organize requests into folders and use patterns—happy path/sad path, endpoint, user-story, or validation-type—for APIs like Restful Booker, employee/contact, bookstore, training inventory, and student transcript.
AI-written summary · about
chapters (22)
- 0:00Intro
- 3:00Kristins Background
- 4:00Paylocity Background
- 4:22Topic Overview
- 4:46Why Get Organized
- 6:01Requests
- 7:41Assertions
- 8:48Bad and Good Assertion Names
- 10:04Where to Put Assertions
- 11:50Naming Conventions
- 13:22Variables
- 15:18Folders
- 16:42Collections
- 17:36Workspace
- 18:42Exercise
- 21:42Organizational Patterns
- 21:59Simple API
- 22:20Happy Path vs Sad Path
- 23:24Endpoint Pattern Example
- 24:49Customer Workflows
- 25:23Student Transcript API
- 25:55Validation Type Pattern
related talks
35mMastering API Ops: Build Scalable Applications
22mRevolutionizing API development: Collaborative workflows with Postman
17mAPI Testing Unlocked
01h 22mWorkshop: How to Create a Test Data-Driven Framework with Postman
28mOptimizing the developer experience through collaboration
21mThe Postman Knocks at Your Door
40mAutomated API Tests with Postman
23mPostman Session: Speed Up Your Developer Workflows with Postman