# Emerging testing best practices for Orbs

**URL:** <https://discuss.circleci.com/t/emerging-testing-best-practices-for-orbs/27474>\
**Category:** Orbs\
**Created:** [January 5, 2019, 1:38am UTC](https://discuss.circleci.com/t/emerging-testing-best-practices-for-orbs/27474 "2019-01-05T01:38:43Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![juanca](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/juanca/32/14598_2.png) [@juanca](https://discuss.circleci.com/u/juanca)\
**Post date:** [January 5, 2019, 4:44am UTC](https://discuss.circleci.com/t/emerging-testing-best-practices-for-orbs/27474/2 "2019-01-05T04:44:41Z")

</div>

I jotted some notes of my experience with testing orbs @ [Testing orbs](https://discuss.circleci.com/t/testing-orbs/26500/4)

The gist:

I set up my CI pipeline to automatically publish my dev orb and then use it in a subsequent job (but **same** workflow) with a dynamically generated configuration file. I need to iterate on this script and publish a release for green master builds but I haven’t had an orb-related task in my daily work activities.

> <https://github.com/mavenlink/orbs/blob/1049bb524553fa28bc555ee68b8c9c7607aad17c/.circleci/config.yml#L19-L42>

---

_[View the full topic](https://discuss.circleci.com/t/emerging-testing-best-practices-for-orbs/27474)._