There are some broad questions, try to answer based on my experience.
Think of Test Harness as an “enabler” that actually does all the work (1) running tests using (2) a test library and (3) generating reports . This will require that your test scripts be designed to handle a variety of (4) test data and (5) test scripts . In fact, when the test posting is installed and preliminary data is prepared (for example, data preparation), someone should be able to click a button or run one command to run all your tests and create reports.
A test harness is most likely a collection of different things that do all of the above. If you wrote unit tests while developing your application, this will be part of the test harness. You also have other tests for the functionality of your application, for example: a user logs on to the site, sees the favorites panel, recent messages and notifications. Then you add a “runner” of views that go through all of your “ test scripts ” and run them (instead of running the tests one at a time). If it seems that the test team is more of a conceptual collection than a separate piece of software, then you get it right :-)
Now my question is, what is the difference between a test case and a script test?
A simple but not entirely correct answer: A Test Case defines the testing objectives, description, prerequisites, steps (descriptive or specific), expected results. A Test Script would be the actual automatic script that you execute to run this test. This is in the context of automation. And that is changing. A lot of.
Which certificates, such as ISTQB, are defined as test cases , are commonly called test cases in some companies and countries. In other cases, test cases are turned over using test scripts when accessing manual testing (when the steps are described in detail, but are not part of the automation bundle). Others say that test cases exclusively mean automatic tests. On the other hand, it can also be argued that several tests can be combined in a test script and vice versa. So the question is, how is the testing procedure suitable?
A test development may have: "Test procedures, test cases, test cases, test data sets, test cases for use in test software."
If you are assuming a relation > (larger / collection) , how would you relate this? A rhetorical question - which depends on where you work, who your client is, etc. It is best to define it with your colleagues / clients and agree to an understanding of the terms, rather than a definition . I am currently testing a script = automatic script based on a pre-existing manual test script or test script.
Also, how do you use the software to test various AUT functions?
You write different tests to test different things. Each test takes certain actions and checks if the result matches AUT, what you expected - If displayed_value == expected_value . For example, the input file could be used to provide data for a test list of test user names and passwords, for example. Or run the same test with different data - log in as another user with different messages, etc.
Take a look at RobotFramework and Selenium . The robot’s framework test (written in text or html files) in combination with the Selenium library allows you to write an automated test that checks something specific ... like checking on a home page. You must write a separate test so that the user can see all his / her messages. The other is for checking notifications. And so on.