Test Plan VS Test Strategy
What is the different between test plan and test strategy?
Did you read the link you posted, and the answer there? Based on your research from that link, and from looking at the answers on this site for that very same question, what do you think the differences are?
A document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning. [IEEE]
A detail of how the test will proceed, who will do the testing, what will be tested, in how much time the test will take place, and to what quality level the test will be performed. [IEEE]
A document prescribing the approach to be taken for intended testing activities. [B. Hetzel]
A high-level description of the test levels to be performed and the testing within those levels for an organization or programme (one or more projects). [ISTQB]
from: All Things Quality: Testing Terms Glossary
Test Plan - It is the way one will follow the whole testing process. You are supposed to test a machine, you need to document the whole process and workflow.
Test Strategy - It works like a course outline which helps project managers, developers and testers to work on key issues which are problems for whole testing process.