程式測試就都有其極限以及隔離情境，在整合驗收時，要求所有相依環境、資料要能符合測試情境是不正確也不必要的，只要有科學的方法能證明程式在指定的隔離情境有依驗收標準進行即可，目前我知道的科學方法就是單元測試與功能測試；早上聽到同事說要在整合測試階段 mock 主機時間去符合整合測試"未來"以及"過去"的情境，加油呀～同事們
Every program test has its limitations and isolated scenarios. During integration and acceptance testing, it is neither correct nor necessary to require that all dependent environments and data perfectly match the test scenarios. As long as there is a scientific method to demonstrate that the program meets the acceptance criteria within specified isolated conditions, that is sufficient. The scientific methods I know of are unit testing and functional testing.
This morning, I heard a colleague mention the idea of mocking the system time during integration testing to simulate "future" and "past" scenarios—keep up the great work, team!
留言