[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Tool for documenting coverage gap
- To: "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>, "users@xxxxxxxxxxxxxxxxxxxxxxx" <users@xxxxxxxxxxxxxxxxxxxxxxx>
- From: Ayan Kumar Halder <ayankuma@xxxxxxx>
- Date: Tue, 1 Apr 2025 18:19:12 +0100
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=amd.com; dmarc=pass action=none header.from=amd.com; dkim=pass header.d=amd.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=efYGWTBTqgGmxeILytMzJC944Xt54sDddXNZF1UtR3w=; b=MuhwJQiFHLJ5iazpHeuC6sz6QebMc6PrTVC0DGo6pDUPK1JZbiU40ML8EXpftYSSUFBLtRpo1LDzCDRsOXyBMqDx//VHriJfcy97SR76VhB3e8fx2TC9tkDf906ltsFeyJ/gQQHsWm3wO3VMR6sO2eXEfCBX0bt5GfI6TjZADtAe0OQuyv1qTsx+WelLeZvhRS0w6e036rNC3FeLqXPepunjGhEauDnFyLAXKpa7AYvsooytyFDUg+jcUYBoh0TsqDUuxGCqlZTMyc363k3MLpuYhA77uiKFmt0xwnw8iTQo1eT6mD4oFKIMfm9lJL3xl2vGtSSgbQi5C4QaoJYneQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=TpU9B3SB+r7f8b1UZSWu5k/+Gl9oHFfTlh9IosJBASZuF0+QBIB500yXoNYCaV8teASof5wSgd8+pEXJroyO1OxQY2umZniO2PWj5lr/mnswUFOMr0Gbsx+gZ8/wOVQK6DIh1x/h/vA2AARazw23BFTjaoJQzATgndkpXNmlBnjLmguV6hjehrc6l3nJG4WaQ64/TaNM4boIO861jRIJ1SAXIR5Jj+smNv8ev20b9r+YYBVzMC/xOqOtqouhJbY+V/B+bdxIfmf3mh+wLa/MtBJ8rf4XMgftnSYOu2xcpVa5zKh8ovWhFq73eTgURA6xCWJTW2xEO/v5YWuH8cLvRw==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=amd.com;
- Cc: "francesco.rossi@xxxxxxxxxxxxx" <francesco.rossi@xxxxxxxxxxxxx>, SHein@xxxxxxxxxx
- Delivery-date: Tue, 01 Apr 2025 17:19:36 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
Hi,
One of the aspects of safety certifying a software is that we need to
produce a coverage report (statement, branch, function and MCDC) and
document the coverage gap (justifying why there is a gap).
Is there a tool which could ingest the coverage output generated by
Gcov, parse it to find instances of coverage gap and enable the
developer to document the reasons for the various coverage gaps ?
The attached screenshot shows a snippet of the coverage report generated
in HITML.
If I were to justify the gaps, I would need to manually document the
functions ( call_psci_cpu_off(), call_psci_system_off()) in a separate
document and explain why there is a gap. I am wondering if there is a
tool which will generate a single report for coverage and justification,
so that the end user sees full coverage.
Kind regards,
Ayan
Attachment:
Screenshot 2025-04-01 at 18.03.07.png
Description: PNG image
|
