Do You Start Testing Right After Receiving the ZIP File? I Prefer to Verify First.

When we’re testing, we often receive ZIP files from engineers, either via cloud links or shared through communication software. It’s quite common to get a file and just dive straight into the testing process.

I used to do the same, but after a few incidents where the contents of the ZIP file didn’t match the expected version—sometimes the version was outdated, or the wrong files were included—I learned the hard way. After spending time testing, only to find out that it wasn’t the correct version, it’s a feeling of frustration and helplessness.

Now, I’ve developed a habit of verifying the files first. Some people manually open the ZIP file to check, but I wrote a small Python script to unzip the file, read the version info inside, and compare it to the version I’m expecting. This way, I feel more confident and save a lot of back-and-forth time.

It’s not something anyone mandates, but for me, testing is not just about executing the process—it’s also about ensuring that we have the right stuff from the beginning. That way, all the effort I put into testing won’t go to waste.

收到壓縮檔就開始測試？我習慣先確認一下。

平常我們測試時，常會收到工程師提供的壓縮檔，可能是透過雲端連結、也可能是在溝通軟體上直接傳送。這種情況其實很常見，大家拿到檔案就直接展開測試流程。

我以前也這樣做，但後來遇過幾次壓縮檔裡的內容跟預期不一致，有時候是版本沒更新，有時候是打包的內容不對。那種明明花了時間測試，最後卻發現不是正確版本的感覺，滿無力的。

所以我後來習慣會先確認。有人會手動打開壓縮檔看看，我則是寫了一個小工具，用 Python 把壓縮檔解開，讀裡面的版本資訊，再跟我手邊預期的版本做比對。這樣比較安心，也省下不少來回確認的時間。

其實這段不是誰規定要做的，但對我來說，測試除了執行流程，更重要的是確保「從一開始就拿對了東西」。這樣我後面的努力才不會白費。