I am scheduled for a technical interview with a company next Wednesday, they provide an electronic payment system for healthcare providers, healthcare clients, and healthcare payers.
I am told by the recruiter to study my SQL and be prepared to make up test cases when given a test topic.
I am also told to explore topics such as
- UI testing
- Functional testing
- Mobility testing
- Performance testing
- Stress testing
- Test automation
- Software Development Life Cycle
Test documentation: What are the necessary components of a good test case? What is a test plan for and what does it consist of?
If you look at a transactional web page what are the observable elements and how do you go about testing them? For example, navigation elements, input fields, buttons, labels...
There are also elements which aren't readily visible like a custom style sheet. What is the roll of "Style Sheets" in a UI implementation?
The two most important topics I must familiarize myself with by next Wednesday are SQL and inventing test cases.
My main questions to you, kind sirs and mams, are, in an SQA interview, what sort of direction should I head in for learning and practicing my SQL? I have only rudimentary knowledge of MySQL from project courses I have taken at my school, I've never worked with SQL before. What are some sources that I can rely on for learning good, practical skills that a good Software Tester should have? What SQL concepts should I absolutely know before I head in?
What kind of test topics should I expect? I have never written any official test cases or test plans before. The sort of testing I do with my code is to just sprinkle print statements all over my projects and eventually track down where the bugs are. I've never even used the debugger in Eclipse, save maybe once or twice. I feel that I am very unprepared for the sort of documented approach to testing software they are going to test me on. How can I prepare myself?