Re: [agile-testing] Continuous Deployment

Wednesday, January 18, 2012

 

Interesting Information.


Regards
Rohan Sarker
+917278539338
+913324288069


On Wed, Jan 18, 2012 at 5:33 AM, Markus Gaertner <mgaertne@googlemail.com> wrote:
 

Besides the remaining useful replies, you might find my write-up of
Kent Beck's talk on Software G-Forces inspiring. He speaks about what
teams do when they get from quarterly releaes down to several releases
per day. Here is a pointer:
http://www.shino.de/2010/11/04/software-g-forces-the-effects-of-acceleration/

Best
Markus



On Wed, Jan 18, 2012 at 10:58, seanalexaoife <coyle.james@gmail.com> wrote:
> Hi,
>
> question for my esteemed colleagues:
>
> Continuous deployment / continuous delivery is a hot topic these days. And one area I'm particularly interested in is 'self-testing software'.
>
> What are people's opinions on what is meant by 'self-testing software'? What does this look like? Is it unit testing by another name? Or is it deeper than that? Does it include the automation of black box tests? And is this now done by the developers? (I'm in a traditional developer / tester agile'ish team).
>
> Thanks
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

--
Dipl.-Inform. Markus Gärtner
http://www.shino.de/blog
http://www.mgaertne.de
http://www.it-agile.de
Twitter: @mgaertne





__._,_.___
Recent Activity:
MARKETPLACE

Stay on top of your group activity without leaving the page you're on - Get the Yahoo! Toolbar now.

.

__,_._,___

0 comments:

Post a Comment