Success Story of Mr. Muntean - Test Engineer shared on 5th Feb 15:

Thank you for sharing these questions on ISTQB - FL on your website I prepared & have passed the CTFL exam. I recommend this website to all who wants to prepare for ISTQB Certifications.

Thank You Very Much, Muntean
Published with the consent of Mr. Muntean

Many a times systematic testing of the software product becomes insufficient and frustrating for the software testing engineers! Reasons being the defects are truly cunning & call for attacking them in equally unpredictable ways.

Here comes the deployment of non-systematic testing techniques as an effective substitute for the systematic testing techniques.

1) Attacks:
It is a type of security testing, meant for testing how resistant a software product is to the people intending to break into it in different ways & for different reasons, may be like incidental mistakes, form fun sake or due to criminal intentions.

Software Testing Genius

The need for secure systems is growing day by day, so is the requirement of powerful and sophisticated security testing. One of the reasons of this is exponential growth of e-commerce & e-business market & at the same time development of more and more applications aimed to get Web access for something or the other.

Security Testing Made Simple by Smart Test Managers

Intelligent software testing managers lay their key focus on the security testing of their system, right from the early stages of the system's life cycle.

The process begins with the drafting of the security test documents. Your starting point can be the security test plan if you were assigned to perform functional testing on a system that is new or new to you, & which can be to familiarize yourself with the product. Generally people prefer one security test plan per release, but you may have one or more functional test plans, mostly depending on the size of your system & its complexity.

Software Testing Genius

Next you can prepare a test case outline or test case document that will outline your test cases to be run with each test case. You can start by noting down & dividing the entire system into various security areas that you may be planning to use at the beginning of your test case documentation. Since test case outline document can grow to a gigantic size, you can have multiple test case outlines for every release. Each one of these can deal with a different security risk or product area.

The next you need to gather all the information you can find on the known product bugs & known security issues. You won't really analyze this information immediately, but you need to have some familiarity with it & have concrete data at hand to refer to later. With this you will have a much better idea of what security issues exist & a list of the ones you specifically want to consider.

System Test Automation Primer-A Must Read for the Test Managers

It is essential for any software testing organization to be more efficient especially in test automation. The reason being automation is a strategic business activity, requiring sound support from the senior management; without which it can doom due to the lack of adequate funds & other resources. Automation is aligned with the business mission and goals and a desire to speed up delivery of the system to the market without compromising its quality. Automation remains a long-term investment and is an on-going process. Results can’t be realized overnight; expectation need to be managed to ensure that it is realistically achievable within a certain time period.

Software Testing Genius

Few Best reasons for system test automation are:
1) Better productivity of software testing engineers

2) Better coverage of regression testing

3) Better reusability of test cases

4) Better consistency in testing