# Use \`uvm\_do macro from uvm\_test

**URL:** <https://verificationacademy.com/forums/t/use-uvm-do-macro-from-uvm-test/36287>\
**Category:** UVM\
**Tags:** UVM, sequence, UVM-uvm\_test, uvm\_do-macros\
**Created:** [July 12, 2019, 2:07pm UTC](https://verificationacademy.com/forums/t/use-uvm-do-macro-from-uvm-test/36287 "2019-07-12T14:07:54Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![DamianS](https://verificationacademy.com/forums/letter_avatar_proxy/v4/letter/d/f6c823/32.png) [@DamianS](https://verificationacademy.com/forums/u/DamianS)\
**Post date:** [July 24, 2019, 8:09am UTC](https://verificationacademy.com/forums/t/use-uvm-do-macro-from-uvm-test/36287/8 "2019-07-24T08:09:25Z")

</div>

_In reply to [dave\_59](https://verificationacademy.com/forums/t/use-uvm-do-macro-from-uvm-test/36287/7):_

Ok thanks for your replies.

So, do you think it’s possible to rewrite the macro accepting only a sequence, removing the SEQ\_OR\_ITEM complication. I still need to identify if the pointer to parent sequence is _null_ or _this_, i.e. if it’s being called from a sequence (_this_) or elsewhere (_null_).

Or is it simply best to avoid the macros. Test writer must use create/create\_item, randomize, start/start\_item, finish\_item.

The problem with the latter is the code mass/read ability, we have some verification environments with 100K+ lines of code and there’s a lot of boiler plate code required to launch a sequence that’s begging for some kind of wrapper… ?

---

_[View the full topic](https://verificationacademy.com/forums/t/use-uvm-do-macro-from-uvm-test/36287)._
