Development Team vs Developers in the new Scrum Guide

A Developer in Scrum is every person, who works on Increment: like programmer, tester (and analyst, etc..)

This is purely a wording change.

Some people viewed the "Development Team" as a sub-team, even though the Scrum Guide was explicit that "Scrum recognizes no sub-teams in the Development Team, regardless of domains that need to be addressed like testing, architecture, operations, or business analysis". The new wording reinforces the fact that there is a single Scrum Team that contains people who can fulfill the responsibilities of the Scrum Master, Product Owner, and Developer roles (or, using the Scrum Guide's language, "accountabilities" - I don't like that term, though).

Developers are "the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.". This includes developers, testers, and any other specialists needed to ensure that you have a Done increment each Sprint.

Thanks Thomas. I was thinking that was the case, but I wanted to hear other people's opinion. 

Our teams consist of both developers and testers. Does anyone have any thoughts on this?

How would you describe their shared accountabilities and commitments?

The team works as a whole. Developers and testers attend PBRs and collaborate as needed on tickets.