# Is it possible to assign a name to a coverpoint?

**URL:** <https://forum.uvvm.org/t/is-it-possible-to-assign-a-name-to-a-coverpoint/520>\
**Category:** Utility Library\
**Created:** [October 2, 2026, 2:20pm UTC](https://forum.uvvm.org/t/is-it-possible-to-assign-a-name-to-a-coverpoint/520 "2026-10-02T14:20:39Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![CharlesGardiner](https://avatars.discourse-cdn.com/v4/letter/c/e495f1/32.png) [@CharlesGardiner](https://forum.uvvm.org/u/CharlesGardiner)\
**Post date:** [October 2, 2026, 2:20pm UTC](https://forum.uvvm.org/t/is-it-possible-to-assign-a-name-to-a-coverpoint/520/1 "2026-10-02T14:20:40Z")

</div>

I’ve built a testbench for a 4-to-1 AXI4 crossbar and added coverage. At he moment there is just one coverpoint, I wnat to see how the transaction lengths are being randomized. The report I get is shown below.

Is there any way to add a used-defined name to the coverpoint, Covpt\_1 is not particularly descriptive. With one cp is’s OK but with many cps it looks like one would have to rely on meaningfull bin names.

> ```auto
> KERNEL: UVVM:      
> # KERNEL: UVVM: ====================================================================================================================================================================
> # KERNEL: UVVM: 5112252.5 ns ***COVERAGE SUMMARY REPORT (VERBOSE): TB seq.***                                                                                                     
> # KERNEL: UVVM: ====================================================================================================================================================================
> # KERNEL: UVVM: Coverpoint: Covpt_1
> # KERNEL: UVVM: Coverage (for goal 100): Bins: 100.00%, Hits: 100.00% 
> # KERNEL: UVVM: --------------------------------------------------------------------------------------------------------------------------------------------------------------------
> # KERNEL: UVVM: BINS HITS MIN HITS HIT COVERAGE NAME ILLEGAL/IGNORE                          
> # KERNEL: UVVM: (0) 63 1 100.00% single -                                 
> # KERNEL: UVVM: (255) 9 1 100.00% max -                                 
> # KERNEL: UVVM: (1 to 15) 989 1 100.00% axi4 length[1] -                                 
> # KERNEL: UVVM: (16 to 30) 64 1 100.00% axi4 length[2] -                                 
> # KERNEL: UVVM: (31 to 46) 68 1 100.00% axi4 length[3] -                                 
> # KERNEL: UVVM: (47 to 62) 76 1 100.00% axi4 length[4] -                                 
> # KERNEL: UVVM: (63 to 78) 62 1 100.00% axi4 length[5] -                                 
> # KERNEL: UVVM: (79 to 94) 71 1 100.00% axi4 length[6] -                                 
> # KERNEL: UVVM: (95 to 110) 88 1 100.00% axi4 length[7] -                                 
> # KERNEL: UVVM: (111 to 126) 67 1 100.00% axi4 length[8] -                                 
> # KERNEL: UVVM: (127 to 142) 66 1 100.00% axi4 length[9] -                                 
> # KERNEL: UVVM: (143 to 158) 55 1 100.00% axi4 length[10] -                                 
> # KERNEL: UVVM: (159 to 174) 60 1 100.00% axi4 length[11] -                                 
> # KERNEL: UVVM: (175 to 190) 54 1 100.00% axi4 length[12] -                                 
> # KERNEL: UVVM: (191 to 206) 68 1 100.00% axi4 length[13] -                                 
> # KERNEL: UVVM: (207 to 222) 50 1 100.00% axi4 length[14] -                                 
> # KERNEL: UVVM: (223 to 238) 74 1 100.00% axi4 length[15] -                                 
> # KERNEL: UVVM: (239 to 254) 64 1 100.00% axi4 length[16] -                                 
> # KERNEL: UVVM: --------------------------------------------------------------------------------------------------------------------------------------------------------------------
> # KERNEL: UVVM: ====================================================================================================================================================================
> 
> ```

---

<div class="post-metadata">

**Author:** ![CharlesGardiner](https://avatars.discourse-cdn.com/v4/letter/c/e495f1/32.png) [@CharlesGardiner](https://forum.uvvm.org/u/CharlesGardiner)\
**Post date:** [October 2, 2026, 2:28pm UTC](https://forum.uvvm.org/t/is-it-possible-to-assign-a-name-to-a-coverpoint/520/2 "2026-10-02T14:28:20Z")

</div>

Oops, a case of documentation overload. Just found the solution

`v_cov_axi4_len.set_name("Transaction Length");`

---

<div class="post-metadata">

**Author:** ![Marius](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.uvvm.org/marius/32/43_2.png) [@Marius](https://forum.uvvm.org/u/Marius)\
**Post date:** [October 6, 2026, 6:22am UTC](https://forum.uvvm.org/t/is-it-possible-to-assign-a-name-to-a-coverpoint/520/3 "2026-10-06T06:22:44Z")

</div>

Hi,

Yes, you can give name to the cover points. The cover points are given a default name if you do not select a name in your testbench.

Br,

Marius