Shared QA responsibilities on an Agile team
For many years our IT development group subscribed to the waterfall software development methodology with segregated pods of programmers specializing in database development, logic layer and presentation layer development. Of course we also had a small quality assurance group which handled all testing responsibilities. Requirements, tasks and bugs were handed back and forth electronically, very little conversation took place, and the process ground painfully on.
How can I introduce QA and break it into parts for various people?
I was recently asked how to do this, specifically:
How can I introduce QA and break it into parts for various people?
I was recently asked how to do this, specifically:
How can I introduce QA and break it into parts for various people?
I was recently asked how to do this, specifically:
How can I introduce QA and break it into parts for various people?
I was recently asked how to do this, specifically:
Are “Compile to JavaScript” Frameworks Hostile to Continuous Integration?
Lately we’ve been looking at ways to improve automated testing and related tooling of our enterprise-level GWT web app. I’ve realized that in some ways, GWT is a bit hostile to automated testing, mainly because of the nature of the long GWT compile times from Java to JS. This makes unit testing somewhat challenging, but it also puts some roadblocks up for testing in a CI environment. I’ve also found out that some of our build and deployment processes are somewhat complicated due to the nature of GWT’s compile process.
Are “Compile to JavaScript” Frameworks Hostile to Continuous Integration?
Lately we’ve been looking at ways to improve automated testing and related tooling of our enterprise-level GWT web app. I’ve realized that in some ways, GWT is a bit hostile to automated testing, mainly because of the nature of the long GWT compile times from Java to JS. This makes unit testing somewhat challenging, but it also puts some roadblocks up for testing in a CI environment. I’ve also found out that some of our build and deployment processes are somewhat complicated due to the nature of GWT’s compile process.
Are “Compile to JavaScript” Frameworks Hostile to Continuous Integration?
Lately we’ve been looking at ways to improve automated testing and related tooling of our enterprise-level GWT web app. I’ve realized that in some ways, GWT is a bit hostile to automated testing, mainly because of the nature of the long GWT compile times from Java to JS. This makes unit testing somewhat challenging, but it also puts some roadblocks up for testing in a CI environment. I’ve also found out that some of our build and deployment processes are somewhat complicated due to the nature of GWT’s compile process.
Are “Compile to JavaScript” Frameworks Hostile to Continuous Integration?
Lately we’ve been looking at ways to improve automated testing and related tooling of our enterprise-level GWT web app. I’ve realized that in some ways, GWT is a bit hostile to automated testing, mainly because of the nature of the long GWT compile times from Java to JS. This makes unit testing somewhat challenging, but it also puts some roadblocks up for testing in a CI environment. I’ve also found out that some of our build and deployment processes are somewhat complicated due to the nature of GWT’s compile process.
Are “Compile to JavaScript” Frameworks Hostile to Continuous Integration?
Lately we’ve been looking at ways to improve automated testing and related tooling of our enterprise-level GWT web app. I’ve realized that in some ways, GWT is a bit hostile to automated testing, mainly because of the nature of the long GWT compile times from Java to JS. This makes unit testing somewhat challenging, but it also puts some roadblocks up for testing in a CI environment. I’ve also found out that some of our build and deployment processes are somewhat complicated due to the nature of GWT’s compile process.