8 Reasons Why Excel or Google Sheets Should Not Be Used as a Test Case Management System

by | Jan 8, 2024 | English, 軟體測試

If we were to talk about the most popular Test Case Management Systems, Excel and Google Sheets might come second and third. Ironically, the first place is held by ‘not having any testing at all,’ which means no need for test management. This isn’t a joke. We surveyed around seventy companies across various sectors like finance, gaming, software development, department stores, and retail. We found that over 70% of these companies don’t have dedicated testing personnel. Testing is either done by the developers themselves or not at all, leaving it to the end-users for acceptance. Even when testing is conducted, it’s often unmanaged.

The issue of ‘not having any testing at all’ is a topic for another day. Today, we’re focusing on why we shouldn’t continue using Excel and Google Sheets for test management.

Have you noticed that the top three methods we’re discussing are not recommended(No testing, Excel, Google Sheet), yet they’re the most commonly practiced? Unfortunately, the main reason for this is cost. Office software, be it Microsoft or Google’s offerings, including free alternatives like OpenOffice and LibreOffice, are standard in most companies. Maximizing utility for the cost is a corporate pursuit. The higher the usage value per cost, the better.

On the flip side, when test engineers need tools for test management but the company doesn’t allocate extra budget, they have to make do with what’s available, often resorting to Excel or Word (yes, some companies use Word for test management).

Let’s dive into why Excel or Google Sheets shouldn’t be used as Test Case Management Systems. Ironically, we’re discussing why not to use these tools, yet they are the most common methods for test management. We can design various templates for management, and each company’s template can be different. This situation stems from a lack of awareness.

Excel and Google Sheets are essentially databases.

The first reason we highlight is that, in today’s tech world, databases are central to applications. Databases store and analyze data to provide meaningful information. Using spreadsheets for test management is like directly managing tests through a database, without an efficient application in between. This is why Excel and Google Sheets can be used for test management but are not ideal, leading to the second point:

These tools are designed for financial, statistical, and scientific purposes.

Using a product designed for specific domains for something else, while not wrong, feels awkward. For example, various types of scissors exist for specific purposes. Using the wrong type of scissors for a task can be troublesome. Similarly, Excel was created for numeric computations, and most of its functions are redundant for test management, as we primarily use it for its tabular format.

The ease of modifying data in tables seems advantageous but can be a significant drawback. Accidental key presses can overwrite data, sometimes irrecoverably. This leads to data loss and additional time spent in rectification.

Incorrect version control is another issue. Although Excel and Google Sheets now have version history, their approach isn’t suited for test management. Imagine a software engineer using Word for coding because of its version history – it’s just as inappropriate for test case management. And even if cell-level version history exists, it’s not the same as managing test case versions.

These tools also hinder team collaboration. Despite the collaborative features of Google Sheets, simultaneous editing and the lack of proper version control can lead to data loss and confusion. A competent test management system records all changes, even simultaneous ones, for traceability and restoration.

File-level management is not suitable for complex projects. Managing thousands of test cases in a spreadsheet is a logistical nightmare, especially when the person responsible leaves or changes. Consistent restructuring of test cases due to varying management styles is a waste of time and resources.

Lack of audit mechanisms and activity logs is another drawback. While these tools can track view and edit histories, they lack the granularity needed for practical use. Tracking individual member contributions and test progress is challenging, especially in remote work environments.

Finally, integration with automated testing is difficult. Imagine trying to backfill automated test results into a spreadsheet – the complexity indicates a problem. This is why most automated tests maintain separate reporting systems, adding another layer of maintenance.

Don’t let tools limit your methods. Focusing solely on Excel and Google Sheets means missing out on more efficient systems. In conclusion, while Excel and Google Sheets are powerful spreadsheet tools, they are not suitable for test case management. Using the wrong tool can hinder staff capabilities and efficiency.

If you’re using Excel and are satisfied with the efficiency, you might be in a stagnant state, unable to see the current problems. This complacency can prevent exploring more efficient alternatives.

Switching to a system designed specifically for testers can ensure an optimized process, saving time for more tests and yielding more product-related data.

文章作者介紹

Fabian Lin

從研發領域叛逃的QA,從小咖變工程總監,我想把業界很多錯誤的認知導正,帶領新鮮人或基層人員往上走,開發平價的測試管理系統Armoury+,在測試的道路上獲得更多成就感(面試不用再只能說找到Bug很有成就感了),歡迎隨時聯繫我。

你也想要分享知識和觀點嗎?KEENLITY目前推出INSIGHT觀點報,誠徵「專欄作家」與「單篇投稿」,點擊連結投稿並了解好處和責任。

精選軟體測試線上課程

邀請您訂閱INSIGHT觀點電子報

Similar Posts

Armoury+:完整的軟體測試六大專業系統

Armoury+:完整的軟體測試六大專業系統

在軟體行業中,你可能聽說過許多商業系統,如 Jira、Figma、Miro、Monday 和 Asana。然而,這些系統主要專注於產品設計和專案管理,對提升軟體測試的效率影響甚微。無論你是否是一名軟體專業人士,你能舉出多少專門針對軟體測試的系統?你可能會說 TestRail、TestLink、Zephyr for Jira 或 Azure DevOps。但你是否注意到,這些系統只解決了測試案例管理的需求,其他測試需求如 API 測試、API 監控以及測試自動化卻沒有得到解決?測試團隊又要想辦法跟公司多拿一筆費用。...

軟體測試聯盟成立:KEENLITY, Blue 與 RTILA 三種藍色色調的美麗相遇

軟體測試聯盟成立:KEENLITY, Blue 與 RTILA 三種藍色色調的美麗相遇

很高興和大家宣布,我們 KEENLITY 與 Blue 和 RTILA 達成國際性的合作!成立軟體測試領域的新聯盟!為台灣企業提供最完善的軟體測試體驗。 KEENLITY Armoury+的軟體測試管理方案開始獲得國際上的認可,產品的可用性、易用性及未來潛力讓很多公司願意合作,並且給予很慷慨的合作提案! 今天正式宣佈!最豐富且最超值的Armoury+訂閱方案來了! 即使與強大的聯盟成員聯手,我們的價格一樣維持平實,我們的願景是 希望測試工程師能夠擁有最棒的工具來提升效率,才能有時間提升自己,並帶給企業更高的價值。 所有訂閱...

Typingmind:用你自己的AI API Key建立私人助理

Typingmind:用你自己的AI API Key建立私人助理

Typingmind其實是KEENLITY的遺珠之一,我們原本想要談合作,但是Typingming的Premium是不提供經銷或是移轉授權的,而高階的Custom服務則完全沒有經銷優惠,反而是要我們先付一筆錢再自己疊價上去賣,看不懂商業邏輯,而不懂的事情不要碰,所以最後也就沒有談成,但Typingmind確實是個不錯的軟體。所以今天這篇不是業配,因為不給合作,我也不給連結了。  當初會找到這個軟體,主要的目的是降低AI訂閱的費用,試著算一下我的使用案例:...

分享好文章給朋友吧!

根據統計,能力越強的人越願意分享文章。你的分享是給作者最大的鼓勵!