Wait, what's a "good citizen"?
A bit of definition:
Software that is a good citizen behaves in a manner consistent with other software, with regard to interaction with other assets with which it interacts.
That's kind of a pompous way of saying that software is behaving like a good citizen when it does what the systems around it expect (e.g., log in a way that centralized logging tools can handle it) and does create excessive load or resource usage (e.g., doesn't attempt to create hundreds of DNS entries when one will do). In other words, this is software that does what it ought to do, and doesn't behave badly.
Software that is being a good citizen does:
- support logging in a common format (e.g., NT Event logs, etc)
- use centralized user or machine management (e.g., Active Directory or NIS)
- does automatic log rolling
- can be configured to start on its own after a power outage or other event
- can be disabled or somehow turned off cleanly (to allow for maintenance, etc)
Software that is being a good citizen does not:
- log excessively (at least, except maybe in debug, which should be used sparingly)
- create excessive traffic on infrastructure servers (DNS, Active Directory, mail, firewall, etc)
- send excessive notifications (e.g., a notification for every user logging in would probably be overkill)
Normally, the good citizen requirement is not explicit. Sometimes you'll find mention of it in requirements indirectly (e.g., must support Active Directory for user interaction), but sometimes you won't. You usually won't find the negative requirements (e.g., doesn't renew its DHCP lease too often) at all. But if you miss one and your software misbehaves, you can bet you'll hear about it! Good citizen requirements are generally assumed, even though they're often not mentioned directly.
As you're testing, ask yourself, "is my software being a good citizen?"