CSE 201 Lecture Notes - Lecture 17: System Testing, User Story, Usability Testing
29 Apr 2019
School
Department
Course
Professor
Document Summary
Cse 201 - lecture 17 - ending and starting iterations. Process improvements, system testing, refactoring of code, cleanup and documentation, design patterns, development environment updates, r&d on new tech, personal dev. System testing: all about reality and system as whole over individual parts. System has to work; using the system. 1) have dedicated end-to-end system testing period. 2) actually let the real users work on system (even if beta release) Emulate real world as much as possible. Small pieces of code, one at a time, isolated from other components and dependencies are minimized. Works great for automated test suites, but can miss bugs that only appear when components interact of live users start banging on system. System testing comes in to hook all together like black box. System testing exercises functionality of system form front-back in real world scenarios. Try to have different set of people doing system testing. Not that devs. aren"t smart; testers bring testing mentality.
