Security Testing… A big challenge!!!

Software is just sets of instructions given to computers to be followed as instructions, and these instructions are designed by human, hence software is as strong or as weak as the developer’s skills. So, the question is … Is there any way to ensure that software is enough strong to sustain in this small but insecure world? The answer may be any of the following:

• Build secure software
• Build secure software
• Build secure software …  

But, again who is going to tell that, software is secure…? Exactly, the answer is what you are thinking right now…The Security Testing Experts. But, if we know the answer then what is the challenge…? The challenge starts from the very beginning i.e. from Planning Phase. The process followed from requirements to release of the product plays main role. Generally the realization of security testing in most of the product comes after some glitch or security breach faced at any moment. But as per the well-known saying that “Precaution is better than cure” fits very well here. Because the Insecure software cost always leads to big failure of the product and starts a game known as BLAME GAME. Whom to blame? Product Manager? Developer? Tester? Or the company as a whole responsible? Does this blaming game properly address the problem? The answer is clear NO.

The best practice is proactive planning for security testing. So it’s very important to make Security Testing as part of SDLC. Pareto principle states that 80% of the effects come from 20% of the causes.  There is no surprise in software 80% of the defects arise from 20% of the design flaws. So addressing the 20% of flaws during design time can mitigate the rest factor considerably.

Facebook Community : https://www.facebook.com/crazzzygig

The Role of Manual Testing in Agile...

The Role of Manual Testing in Agile...
Although Automation Testing is a core recommendation in Agile Development, because of Agile's speed, and Speed needs Process. A fast feedback from Quality Assurance team is very important for continuous improvement and timely delivery of Quality Product. But after all these facts,  "Manual Testing" can't be taken as less important part of the process. There may be many edges where a product can slip just because of less focus on Manual Testing.
Few minor things, which can be risk in later stage of the product development process:
1. A continuous dependency on automation can lead the teams to be disconnected with the product.
2. Quality of the product can't be decided just upon the automation. It may be a big risk.
3. It is impossible to improve the product features with respect to user experience.
4. Good understanding of business requirements and to know the product from user perspective is very important for Quality Product.

Facebook Community : https://www.facebook.com/crazzzygig

An open place for Software Testing discussions, Concepts and New Ideas.

After spending almost 2 years in industry, I have learned many things which I never thought in my college days and in the same way the things which we can learn or improve by discussing, sharing and by bringing the concepts and ideas we have or we face in day to day work, cannot be improved by keeping it to ourselves (either Problem or Solution).

Let’s join our hands and share our knowledge.

Facebook Community : https://www.facebook.com/crazzzygig