Home/ Questions/Q 580447
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T14:28:26+00:00

I have been developing an internal framework which is designed with bunch of Perl

  • 0

I have been developing an internal framework which is designed with bunch of Perl modules. All these modules are dependent on a single module that exposes some Win32 functionality. For e.g. A, B, C, D, etc modules all depend on a single module Z. So all these modules will import by “use MyFramework::Z”. All these modules A,B,C etc can be used individually & arenot dependent on any other framework modules.

Now, with that simple design in mind – how do I design my unit tests. I am planning to use Test::More to do all the unit tests. Should I write individual unit tests for each module? There are 25 different modules that belong to this framework. Any suggestions?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Unit tests for Z should cover the Win32 functionality.

    Unit tests for A should cover the functionality of A that isn’t covered in Z.
    Repeat for B, C, D, and so on.

    If you find that C, E, and G are doing similar things and you are writing nearly identical unit tests, that is the signal to refactor — extract common components up to a higher level (e.g., module CEG) and just leave and test the special parts of C, E, and G in their original modules.

    • 0