• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

mbland / elistman / 5250411837
100%

Build:
DEFAULT BRANCH: main
Ran 13 Jun 2023 02:01AM UTC
Jobs 1
Files 38
Run time 1s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

13 Jun 2023 01:59AM UTC coverage: 100.0%. Remained the same
5250411837

push

github

mbland
Consolidate ProdAgent tests, some implementation

The duplication in the tests started to bother me. This is a relatively
unusual case whereby testing several closely intertwined functions
through a single public function is less complicated than testing each
separately. This is because each function is fairly straightforward and
there's a specific dependency pattern between them:

                                 Send
                            (uncomplicated)
                                   |
            Validate message and create message template
                            (uncomplicated)
                                   |
            +------------------------------------------+
            |                                          |
      sendToEntireList                      sendToSpecificRecipients
       (complicated)                             (complicated)
            |                                          |
            +------------------------------------------+
                                   |
                             sendOneEmail
                            (uncomplicated)

Most of the functions are relatively straightforward. The complicated
functions share context (validating the message and creating a template)
and infrastructure (the database and mailer). Both also ultimately call
the same lower level function. The dependencies don't fan out very far,
and the logic fans back into the same fundamental operation.

Consequently, it's less work and less redundant in this case to test
everything through the single Send entrypoint after all. I'm sure
there's an even better, more clear way to express this, but this is the
best I have for now.

13 of 13 new or added lines in 1 file covered. (100.0%)

2220 of 2220 relevant lines covered (100.0%)

15.99 hits per line

Jobs
ID Job ID Ran Files Coverage
1 5250411837.1 13 Jun 2023 02:01AM UTC 38
100.0
GitHub Action Run
Source Files on build 5250411837
  • Tree
  • List 38
  • Changed 4
  • Source Changed 3
  • Coverage Changed 4
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #5250411837
  • e0e24ef2 on github
  • Prev Build on main (#5247385822)
  • Next Build on main (#5257939760)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc