Comments on: Ten Essential Practices of Continuous Integration http://tynerblain.com/blog/2006/05/09/ten-essential-practices-of-continuous-integration/ Software product success. Sat, 19 May 2012 12:04:06 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Juan Carlos http://tynerblain.com/blog/2006/05/09/ten-essential-practices-of-continuous-integration/comment-page-1/#comment-370205 Juan Carlos Mon, 12 May 2008 16:47:32 +0000 http://tynerblain.com/blog/2006/05/09/ten-essential-practices-of-continuous-integration/#comment-370205 The list of the test-results its very good to make the trazability matrix. In the continous integration we have to count that some requeriments its not completed in the first Iteration or integration. the test plan have to say it!!. Not all practices, mencionated, are avaliable on the first integration. Example, many times the installer o the deploy of the app its the last work to delivery. I have a question, do you a tool to make when delivery the producto to the tester run the unit test? The list of the test-results its very good to make the trazability matrix. In the continous integration we have to count that some requeriments its not completed in the first Iteration or integration. the test plan have to say it!!.

Not all practices, mencionated, are avaliable on the first integration. Example, many times the installer o the deploy of the app its the last work to delivery.

I have a question, do you a tool to make when delivery the producto to the tester run the unit test?

]]> By: Scott Sehlhorst http://tynerblain.com/blog/2006/05/09/ten-essential-practices-of-continuous-integration/comment-page-1/#comment-2079 Scott Sehlhorst Fri, 12 May 2006 16:13:09 +0000 http://tynerblain.com/blog/2006/05/09/ten-essential-practices-of-continuous-integration/#comment-2079 Thanks Jason, for the comments and the long-time reading and referencing of our site. I really appreciate it. Sorry to everyone who tried to follow the Calavista link before, it was broken, but should be fixed now. Jason, I haven't personally done any obfuscation stuff in any of my projects, so I don't have an answer from experience. That said, I think it makes sense to include it as a precompilation step within the automated build. Automated testing should be of the post-obfuscaation binary, to eliminate the risk of the obfuscation introducing any bugs. It would make sense to be able to trigger an automated test run of the non-obfuscated code in the event of bugs being found during the automated testing. Just my thoughts on how I would approach it. I would love to hear from anyone who's currently doing obfuscation. Thanks Jason, for the comments and the long-time reading and referencing of our site. I really appreciate it.

Sorry to everyone who tried to follow the Calavista link before, it was broken, but should be fixed now.

Jason, I haven’t personally done any obfuscation stuff in any of my projects, so I don’t have an answer from experience. That said, I think it makes sense to include it as a precompilation step within the automated build. Automated testing should be of the post-obfuscaation binary, to eliminate the risk of the obfuscation introducing any bugs.

It would make sense to be able to trigger an automated test run of the non-obfuscated code in the event of bugs being found during the automated testing.

Just my thoughts on how I would approach it. I would love to hear from anyone who’s currently doing obfuscation.

]]> By: Jason Haley http://tynerblain.com/blog/2006/05/09/ten-essential-practices-of-continuous-integration/comment-page-1/#comment-2028 Jason Haley Wed, 10 May 2006 20:37:36 +0000 http://tynerblain.com/blog/2006/05/09/ten-essential-practices-of-continuous-integration/#comment-2028 Very nice list. If the production product is going to be obfuscated, where would you add in the obfuscation and integration testing? I'm starting to really look into CI and how obfuscation should/could fit into the cycle if needed, so I'm curious as to what your thoughts or suggestions are on it. It seems most people don't deal with the details when it comes to obfuscation (sort of like demos never have error/exception handling code in them) or they just don't need to obfuscate their code (ie. server side apps). Very nice list. If the production product is going to be obfuscated, where would you add in the obfuscation and integration testing?

I’m starting to really look into CI and how obfuscation should/could fit into the cycle if needed, so I’m curious as to what your thoughts or suggestions are on it.

It seems most people don’t deal with the details when it comes to obfuscation (sort of like demos never have error/exception handling code in them) or they just don’t need to obfuscate their code (ie. server side apps).

]]>