I guess it depends on what's more important to you: being a proud developer (and interpreting being a developer as "I ain't do testing stuff, only write code"), or delivering working software as part of a team (which would imply that everyone is helping out each other as needed, even by doing unpleasant or boring stuff when it just has to be done).

So even though you are employed as a "software developer", in Scrum your job title may not be that important.

> A Scrum team in a Scrum environment does not include any of the
> traditional software engineering roles such as programmer, designer,
> tester or architect. Everyone on the project works together to
> complete the set of work they have collectively committed to complete
> within a sprint. Because of this, Scrum teams develop a deep form of
> camaraderie and a feeling that "we're all in this together."

(Quoted from [here][1].)

In other words, if Joe is held back with his task and can't complete it till the end of the sprint, it is of no use to the team if Jim is fully done with "his tasks" and sitting idle, or is working on something less valuable rather than helping Joe.

So yes, in a well functioning Scrum team, even though members may have different primary expertise areas, still developers occasionally (or even often) do testing, testers may help out writing SQL scripts, DBAs sometimes jump in to configure a development server etc. etc.

In fact, I used to work in a Scrum team where we had no dedicated QA personnel at all; only four developers. And we did all the testing ourselves. It included building an automated, shell script based testing framework alongside developing the product and writing our unit tests. And actually it was much more fun than you might expect. But of course, the most fun was actually to see the project succeed :-)


  [1]: http://www.mountaingoatsoftware.com/agile/scrum/team