Skip to main content

Lost trust in manual QA

At my employer's startup the product footprint has grown so big that I have lost trust in manual QA.  Take an e.g. of today,  last night QA found an issue and then my team mate fixed it, before I woke up I saw that QA passed the ticket in flying colors and they did tested many things like update user, bulk update user.

As there is a release today night, I did a detailed code review of the fix and immediately within 2 minutes I see an issue in the bulk update and the problem was that original developer didnt used DRY. So the team mate had fixed update user and from UI the bulk action would still call updateUser. The other bulk update would be called only when you do import CSV or some other public api.

The point being I have lost trust in manual QA because they really cant regress a ticket using all possible combinations in the short amount of time.

We do a release every 3 weeks and in 2 week is dev and 2 week is QA (2nd week is overlap), but in those 2 week we are always scrambling to get our act in shape so corners has to be cut.  Many times I see QA raising tickets after its live in prod.

The only way here is to remove the human touch point from equation if we want to maintain the same release velocity and code quality.


Popular posts from this blog

RabbitMQ java clients for beginners

Here is a sample of a consumer and producer example for RabbitMQ. The steps are
Download ErlangDownload Rabbit MQ ServerDownload Rabbit MQ Java client jarsCompile and run the below two class and you are done.
This sample create a Durable Exchange, Queue and a Message. You will have to start the consumer first before you start the for the first time.

For more information on AMQP, Exchanges, Queues, read this excellent tutorial
import com.rabbitmq.client.Connection; import com.rabbitmq.client.Channel; import com.rabbitmq.client.*; public class RabbitMQProducer { public static void main(String []args) throws Exception { ConnectionFactory factory = new ConnectionFactory(); factory.setUsername("guest"); factory.setPassword("guest"); factory.setVirtualHost("/"); factory.setHost(""); factory.setPort(5672); Conne…

Spring query timeout or transaction timeout

If you are using spring to manage transactions then you can specify default transaction timeout using

    <bean id="transactionManager"
        <property name="dataSource" ref="dataSource" />
        <property name="defaultTimeout" value="30" /> <!--30 sec--->             

or you can override the timeout in the annotation

    @Transactional(readOnly = false, timeout=30)

or if you are doing it programatic transactions then you can do

DataSourceTransactionManager transactionManager = new DataSourceTransactionManager(dataSource);

 or you can override the timeout for one particular transaction

TransactionTemplate transactionTemplate = new TransactionTemplate();

Python adding pid file

I have a thumbnail generator that launches multiple processes and the correct way to shut it down is to send kill -HUP to the parent process. To automate I had to write a pid file from python, it was a piece of cake
def writePidFile(): pid = str(os.getpid()) f = open('', 'w') f.write(pid) f.close()