| || |
Re: Object-Oriented Methodology and HTML
Mimi, we would be doing you little help if we just gave you the answers because then we would be guilty of potentially getting you in over your head at a job where you did not really know the material. Knowing the answers to these types of questions does not automatically mean you could do this stuff in a job. Your average interviewer/employer would quickly find that out.
With that, let me just give you what I think is a little start in the right direction.
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by juz0n0:
1. What object-oriented methodology and resource can be used in the QA field?<HR></BLOCKQUOTE>
There are many such methodologies (although sometimes they are not strictly methodologies, but rather processes). This is a very general question and it seems an odd one for an interviewer to ask, at least in this fashion. With the term "resource", are they talking about tool resources? Process resourses? Testing resources? There is no way to tell based on this question.
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>2. How does HTML works (interacts) with QA?<HR></BLOCKQUOTE>
Again, this question really does not make all that much sense, at least as asked. Perhaps the intention was more along the lines of how does one go about testing HTML or assuring the quality of Web pages and Web applications that use HTML markup. Again, this is a very large question that does not commend itself to a simple one or two line answer.
What I would recommend, since you have worked as a QA staffer in some capacity, is to think about what these questions mean and how you could best go about learning some of this material so that you could not only give accurate answers but know what the answers mean. For example, I will tell you that one type of "object-oriented methodology" is something called the Unified Modeling Language (UML). Have I just given away the answer? Well, maybe - or at least one possible answer. But there is so much to the UML that if you were to answer this to an employer, they would assume you knew about the UML and might ask you further questions regarding it. Are you prepared to answer those questions? My guess is probably not. But now you at least have something you can be looking into to learn about this kind of thing.
Likewise with the HTML question, assuming that this is more asking how someone might test HTML (or other types of markup), think about what HTML is the basis of: Web pages and Web applications. In that case, can you think of some ways as to how you would test those things?
Do you see where I am coming from here? I am not trying to blow off your question but I am hoping you see that just giving you answers (a) is not really possible given the way the questions are stated, and (b) would not be the most helpful to you.
Object-Oriented Methodology and HTML
I have worked with one Company as QA (contract). However, I am still looking for QA position. I have been asked some of questions during interview. Does any one can help me to answer the following questions correctly?
1. What object-oriented methodology and resource can be used in the QA field?
2. How does HTML works (interacts) with QA?
Thanks a lot!