Why do you choose Software Testing – as your Career

Career in Software Testing

A Career in Testing Scope of getting job is especially high, No need to depend on any technology, Testing will be there for ever could be as pleasing and satisfying as any other career for motivated and capable people.

1. Testing offers sufficient technical challenges for an interested professional to continuously learn, enrich his or her knowledge, and achieve greater heights of personal satisfaction as well as product quality and fulfillment.

2. I like software testing because it is NOT straightforward. It's not like you need to do 100 things for small applications and 10,000 things for bigger applications and done with it. And it's not like you're good if you have a functional tests  and system tests. It's not about the quantity; it is actually about the quality. when we're testing something. Different aspects of problems that the application solves, technology that is used, business expectations, threats, performance, dead line date, project team, process, and etc. Finding best possible testing strategy and execution around this environment is great fun.

3. Development engineers be likely to focus on particular Requirements. Test Engineers, in compare, generally require a more social factors understanding of the product fairly than be extent to a single module or component. This gives an boundary to test engineers at becoming domain specialist.
   

3.  Most Development happens in a compartmentalized manner, Testing may even require a much deeper understanding of the interactions and independencies amongst multiple domains to be able to simulate real life scenarios.
   

3.  I would say this is more of test execution fun. This is not about writing automation code I would say. Coming up with best test execution strategy is great fun. What kind of tool is useful for data driven testing? How about model based testing? What's best test automation strategy for agile process? Experience in several different test framework and tools. Quick experiment on new tools. What if we just choose to go with manual for testing this feature? How can we represent our test results and communicate with the team? This requires endless learning. Learn to design good test framework,  learn new languages and new tools, learn how to represent test results, learn how to optimize test execution time, learn, learn and learn.
   
   by ,
   QA Trainer.

Difference between Test Plan and Test Strategy

Test Plan - A software project test plan is a document that describes the objectives, scope, approach, and focus of a software testing effort
The purpose of the Master Test Plan, as stated by the IEEE Std 829 is to provide an overall test planning and test management document for multiple levels of test

Test Strategy – Test Strategy or Test Approach is a set of guide lines that describes test design. Test strategy says - How testing is going to be performed? What will be the test architecture?

Test Strategy can be at two levels – Company/Organization Level and Project Level. For e,g, If company is product based, then there can be a general test strategy for testing their software products. Same strategy can be implemented (with/without  some modifications) at project level whenever a new project comes.
Well,  Arun  introduces
Test Plan: the set of ideas that guide a test project
Test Strategy: the set of ideas that guide test design
Test Logistics: the set of ideas that guide the application of resources to fulfill a test strategy
I find these ideas to be a useful jumping off point. Here are some implications:
The test plan is the sum of test strategy and test logistics.
The test plan document does not necessarily contain a test plan.      This is because many test plan documents are created by people who are following templates without understanding them, or writing things to please their bosses, without knowing how to fulfill their promises, or simply because it once was a genuine test plan but now is obsolete.
Conversely, a genuine test plan is not necessarily documented. This is because new ideas may occur to you each day that change how you test.
Conclusion:
Is Test Plan document is required for testing?
Test Plan covers – What needs to be tested, How testing is going to be performed? Resources needed for testing, Timelines and Risk associated.
For efficient and effective test planning we don’t really need IEEE-829 template for test plan. Planning can be done without test plan document also. Identify your test Approach (strategy) and go with your testing. Many test plans are being created just for the sake of processes.
Note – We are not against Test Plan documents. Use test plan documents if they really contains some useful information.
In the upcoming posts, we will discuss points to take care while deciding a test strategy & guide to prepare a Test Plan.
Related Posts:
·           Test Strategy
·           Defining a Test Strategy
·           Creating a Test Strategy

·           Effective Handbook for Implementing Test Strategies