Category Archive for Release Management

Github

15 Jul, 2009  15 Comments

I am starting a project for a large corporation. It is up to the developers to decide what SCM to use. Are there any concerns out there to use a provider like Github?

Post to Twitter Tweet This Post

TDD Test Driven Development

3 Jun, 2009  No Comment

I have worked on TDD in one project

Pros:
1. Gives good test coverage.
2. Gives a better understanding of the requirements (and not when the UAT is in progress).
3. Increases the code efficiency – you know what the module is supposed to do.
4. Encourages the developer to read the documents.

Cons:
1. Requires co-ordination effort between tester and developer.(trust me its difficult in the start). This also does not give the liberty for the most cranky dev/test resources to work independently over-night.
2. Sometimes the testing needs to wait for dev and vice-versa.

Post to Twitter Tweet This Post

What would be the right approach or main reasons when convincing a client to switch from the classic waterfall to Agile? What would be his main benefits (business wise)?

8 Apr, 2009  11 Comments

Post to Twitter Tweet This Post

QA Mailing Lists and User Groups

10 Nov, 2008  96 Comments

Mailing Lists and User Groups

Unit Testing

3 Nov, 2008  No Comment

Unit Testing: Still Widely Informal

This poll examined how organizations perform unit testing. Is it an
informal activity that is done before integration if there is some time
left after programming or is it the key element of the development
effort? The question was: How is unit testing performed at your
location?

Proportion 2008 2006
Unit testing is not performed 17% 13%
Unit testing is informal 40% 46%
Unit tests cases are documented  9% 11%
Unit tests cases and their executions are documented 14% 16%
We use a Test Driven Development approach 20% 14%

Despite the fact that the number of TDD adopters has grown nicely
since the previous survey, you can notice that unit testing is still
widely conducted in a informal manner, when it is not simply ignored by
developers. This could sound weird when many people announced a general
adoption of the agile approaches, but the results of our survey are
similar to many other polls on the same topic.

Comparing the two surveys, it seems that people that were already
doing unit testing formally have switched towards a TDD approach. People
that don’t do unit testing have different reasons. Some will consider
simply that they don’t add value to their development process, which is
sometimes difficult to believe. For others, it is the lack of time, a
reason more easier to understand ;o) Many complains that unit test are
hard to write, but creating a good unit test is a proof that you
understand what your code should do. I agree however, that it could be
difficult to maintain large libraries of unit testing scripts if
requirements are changing constantly. In the "good" reasons
not to perform unit testing, some thinks for instance that the client
side of Web application is not suited for this kind of tests. There are
also some organizations that have separate testing teams. Their
developers will rely entirely on the QA guys to test their application.
You can also consider that when the software has a very limited life
expectancy, it is not worth making unit tests.

Post to Twitter Tweet This Post

Solutions for Automating and Managing Change

26 Sep, 2008  No Comment

What tools are the best for Change Management?

Post to Twitter Tweet This Post

What is SCM

24 Sep, 2008  No Comment

control of modifications changes to the project plan by the programmers during the development phase. Software Configuration Management is also called Software Control Management. I would like to discuss SCM tools and benefits of each

Post to Twitter Tweet This Post