# 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:** 7

<div class="post-metadata">

**Author:** ![dave\_59](https://verificationacademy.com/forums/user_avatar/verificationacademy.com/dave_59/32/4499_2.png) [@dave\_59](https://verificationacademy.com/forums/u/dave_59)\
**Post date:** [July 19, 2019, 8:33am UTC](https://verificationacademy.com/forums/t/use-uvm-do-macro-from-uvm-test/36287/7 "2019-07-19T08:33:36Z")

</div>

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

I think the UVM macros confuses the two concepts of sequences and sequence\_items. (probably leftover from OVM)

A sequence is a handle to a procedural body of code (hence the **body()** method). See the [functon pointer OOP design pattern)](https://en.wikipedia.org/wiki/Function_object). There is no arbitration required for sequences.

A sequence\_item is a transaction of data that you want dest to a driver. Arbitration gets manages by a sequencer. You can start sequences from components like the test, and from other sequences.

---

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