{"id":51,"date":"2026-02-24T23:54:59","date_gmt":"2026-02-24T23:54:59","guid":{"rendered":"https:\/\/sites.nd.edu\/softwaretesting\/?page_id=51"},"modified":"2026-03-30T13:15:08","modified_gmt":"2026-03-30T13:15:08","slug":"saas-vs-custom-development-testing","status":"publish","type":"page","link":"https:\/\/sites.nd.edu\/softwaretesting\/saas-vs-custom-development-testing\/","title":{"rendered":"SaaS vs Custom Development Testing"},"content":{"rendered":"\n<p>Testing strategies differ depending on whether your software is a vendor-managed SaaS (Software as a Service) product or a custom-built system. Understanding the differences helps ensure proper coverage, reduce risks, and optimize resources.<\/p>\n\n\n\n<p>The table below provides a high-level overview:<\/p>\n\n\n\n<table id=\"tablepress-4\" class=\"tablepress tablepress-id-4\">\n<thead>\n<tr class=\"row-1\">\n\t<th class=\"column-1\">Aspect<\/th><th class=\"column-2\">SaaS (Customer Perspective)<\/th><th class=\"column-3\">Custom Development<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"row-striping row-hover\">\n<tr class=\"row-2\">\n\t<td class=\"column-1\"><strong>Ownership<\/strong><\/td><td class=\"column-2\">Vendor owns code<\/td><td class=\"column-3\">Customer owns code<\/td>\n<\/tr>\n<tr class=\"row-3\">\n\t<td class=\"column-1\"><strong>Focus<\/strong><\/td><td class=\"column-2\">Configuration, integrations, key business workflows<\/td><td class=\"column-3\">Functional correctness, end-to-end quality<\/td>\n<\/tr>\n<tr class=\"row-4\">\n\t<td class=\"column-1\"><strong>Risk<\/strong><\/td><td class=\"column-2\">Vendor updates may disrupt operations<\/td><td class=\"column-3\">Defects in new or modified software code<\/td>\n<\/tr>\n<tr class=\"row-5\">\n\t<td class=\"column-1\"><strong>Timing<\/strong><\/td><td class=\"column-2\">During implementation and after vendor updates<\/td><td class=\"column-3\">Throughout SDLC (Software Development Lifecycle) until go-live<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<!-- #tablepress-4 from cache -->\n\n\n\n<p>The tables below depict the typical product types along with the applicable types of testing and who is responsible each:<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong><em>New SaaS Product<\/em><\/strong><\/h2>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"538\" src=\"https:\/\/sites.nd.edu\/softwaretesting\/files\/2026\/03\/SaaS-New-1024x538.jpg\" alt=\"\" class=\"wp-image-465\" srcset=\"https:\/\/sites.nd.edu\/softwaretesting\/files\/2026\/03\/SaaS-New-1024x538.jpg 1024w, https:\/\/sites.nd.edu\/softwaretesting\/files\/2026\/03\/SaaS-New-300x158.jpg 300w, https:\/\/sites.nd.edu\/softwaretesting\/files\/2026\/03\/SaaS-New-768x403.jpg 768w, https:\/\/sites.nd.edu\/softwaretesting\/files\/2026\/03\/SaaS-New.jpg 1188w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Unit Testing: Applicable only if modifications will be made to accommodate customer-specific needs<\/li>\n\n\n\n<li>Performance Testing: Vendor should provide a SLA (Service Level Agreement) for product performance\n<ul class=\"wp-block-list\">\n<li>If the system will handle heavy load\/peak processing (e.g., Class Registration), the ND customer group should consider performing their own load testing for the applicable business function(s)<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Security Testing: Typically involves the assigned ND Developer or Technical Lead (and possibly Identity Access Management or Information Security for consultation) in conjunction with the Vendor<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong><em>New Custom Developed Product<\/em><\/strong><\/h2>\n\n\n\n<figure class=\"wp-block-image size-full is-resized\"><img loading=\"lazy\" decoding=\"async\" width=\"794\" height=\"496\" src=\"https:\/\/sites.nd.edu\/softwaretesting\/files\/2026\/02\/Custom-Developed.jpg\" alt=\"\" class=\"wp-image-73\" style=\"aspect-ratio:1.6008253788236777;width:600px;height:auto\" srcset=\"https:\/\/sites.nd.edu\/softwaretesting\/files\/2026\/02\/Custom-Developed.jpg 794w, https:\/\/sites.nd.edu\/softwaretesting\/files\/2026\/02\/Custom-Developed-300x187.jpg 300w, https:\/\/sites.nd.edu\/softwaretesting\/files\/2026\/02\/Custom-Developed-768x480.jpg 768w\" sizes=\"auto, (max-width: 794px) 100vw, 794px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><em><strong>Product Upgrade<\/strong><\/em> (<em><strong>SaaS or Custom Developed<\/strong><\/em>)<\/h2>\n\n\n\n<figure class=\"wp-block-image size-full is-resized\"><img loading=\"lazy\" decoding=\"async\" width=\"529\" height=\"494\" src=\"https:\/\/sites.nd.edu\/softwaretesting\/files\/2026\/02\/System-Upgrades.jpg\" alt=\"\" class=\"wp-image-74\" style=\"aspect-ratio:1.0708524434603828;width:433px;height:auto\" srcset=\"https:\/\/sites.nd.edu\/softwaretesting\/files\/2026\/02\/System-Upgrades.jpg 529w, https:\/\/sites.nd.edu\/softwaretesting\/files\/2026\/02\/System-Upgrades-300x280.jpg 300w\" sizes=\"auto, (max-width: 529px) 100vw, 529px\" \/><\/figure>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Unit Testing: Applicable only if code modifications are made<\/li>\n\n\n\n<li>Regression Testing: This includes testing of any new functionality or features and update of existing regression test cases<\/li>\n<\/ul>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Testing strategies differ depending on whether your software is a vendor-managed SaaS (Software as a Service) product or a custom-built system. Understanding the differences helps ensure proper coverage, reduce risks, and optimize resources. The table below provides a high-level overview: The tables below depict the typical product types along with the applicable types of testing [&hellip;]<\/p>\n","protected":false},"author":4975,"featured_media":0,"parent":0,"menu_order":4,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-51","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/sites.nd.edu\/softwaretesting\/wp-json\/wp\/v2\/pages\/51","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sites.nd.edu\/softwaretesting\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/sites.nd.edu\/softwaretesting\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/sites.nd.edu\/softwaretesting\/wp-json\/wp\/v2\/users\/4975"}],"replies":[{"embeddable":true,"href":"https:\/\/sites.nd.edu\/softwaretesting\/wp-json\/wp\/v2\/comments?post=51"}],"version-history":[{"count":11,"href":"https:\/\/sites.nd.edu\/softwaretesting\/wp-json\/wp\/v2\/pages\/51\/revisions"}],"predecessor-version":[{"id":466,"href":"https:\/\/sites.nd.edu\/softwaretesting\/wp-json\/wp\/v2\/pages\/51\/revisions\/466"}],"wp:attachment":[{"href":"https:\/\/sites.nd.edu\/softwaretesting\/wp-json\/wp\/v2\/media?parent=51"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}