# PocketIC: Testing Canisters in Python 🐍

**URL:** <https://forum.dfinity.org/t/pocketic-testing-canisters-in-python/22490>\
**Category:** Developers\
**Created:** [September 1, 2023, 2:33pm UTC](https://forum.dfinity.org/t/pocketic-testing-canisters-in-python/22490 "2023-09-01T14:33:46Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![gravity\_vi](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/gravity_vi/32/35810_2.png) [@gravity\_vi](https://forum.dfinity.org/u/gravity_vi)\
**Post date:** [January 15, 2024, 9:14am UTC](https://forum.dfinity.org/t/pocketic-testing-canisters-in-python/22490/2 "2024-01-15T09:14:08Z")

</div>

We are facing an issue with `pocket_ic`. In our scenario a `user_index` canister manages all canister for users. And when the upgrades run for `user_index` canister it also upgrades all the individual user canisters in` post_upgrade`. Previously we used to use `state_machine` to test this scenario and one call to tick command with `advance_time` used to upgrade `user_index` and all individual canisters. With the recent move to pocket\_ic `tick` call is not upgrading all the canisters. Is there a way to determine how many tick calls would needed for the completed upgrade process.

---

_[View the full topic](https://forum.dfinity.org/t/pocketic-testing-canisters-in-python/22490)._
