# How to test part cooling fan

**URL:** <https://klipper.discourse.group/t/how-to-test-part-cooling-fan/5140>\
**Category:** General Discussion\
**Created:** [November 28, 2022, 3:18pm UTC](https://klipper.discourse.group/t/how-to-test-part-cooling-fan/5140 "2022-11-28T15:18:51Z")\
**Posts on this page:** 4\
**Page:** 2

<div class="post-metadata">

**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\
**Post date:** [November 29, 2022, 7:39pm UTC](https://klipper.discourse.group/t/how-to-test-part-cooling-fan/5140/21 "2022-11-29T19:39:19Z")

</div>

> [@mykepredko](#):
>
> What is your criteria for deciding which user bugs should be caught in software?

Not my call anyway, I just clean up here 😉

 ![image](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/a/a3af98e3afbee2e94d62ccd8852e07c70d95b17c.png)

---

<div class="post-metadata">

**Author:** ![mykepredko](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/mykepredko/32/2085_2.png) [@mykepredko](https://klipper.discourse.group/u/mykepredko)\
**Post date:** [November 29, 2022, 8:07pm UTC](https://klipper.discourse.group/t/how-to-test-part-cooling-fan/5140/22 "2022-11-29T20:07:38Z")

</div>

For the most part I would agree with you but I’ve had a lot of luck with automating unit and functional tests with huge amounts of time freed up and generally very precise indications of where the problems have come in.

---

<div class="post-metadata">

**Author:** ![koconnor](https://avatars.discourse-cdn.com/v4/letter/k/aca169/32.png) [@koconnor](https://klipper.discourse.group/u/koconnor)\
**Post date:** [December 5, 2022, 5:00pm UTC](https://klipper.discourse.group/t/how-to-test-part-cooling-fan/5140/23 "2022-12-05T17:00:13Z")

</div>

FWIW, there are two issues complicating checking of config files:

1. We use an external library for parsing the config file, and there isn’t much desire to reimplement that library for a few minor tweaks in behavior.
2. I don’t know of any user that would intentionally override an option in a later config section. (This does cause confusion for users and this is not the first report I’ve seen of it.) However, there are many users that would like to be able to duplicate a config section multiple times and only set some options in each instance of that config section. The “ratrig configs” are an example of this. More recent versions of the python config parsing libraries do have the ability to prevent duplicate config sections, but don’t (to my knowledge) have the ability to flag just duplicate options in duplicate config sections.

Cheers,  
-Kevin

---

<div class="post-metadata">

**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\
**Post date:** [June 18, 2024, 1:44pm UTC](https://klipper.discourse.group/t/how-to-test-part-cooling-fan/5140/24 "2024-06-18T13:44:09Z")

</div>



[Previous page](https://klipper.discourse.group/t/how-to-test-part-cooling-fan/5140.md?page=1)