SQC Vs. SQA

Software Quality Control Software Quality Assurance


Is perceived as a professional role Is perceived as management’s eyes and
ears.

Has well-defined technical goals Has no history of saving anyone yet

Has leverage to stop the show Has fuzzy alignment with the project’s
goals.

Has authority with the developers Has no leverage to stop anything

Is aligned with the project goals Has few opportunities to show proficiency
before the problem

What is the difference among Testing, QA and QC

Quality Assurance: A set of activities designed to ensure that the development and/or maintenance process is adequate to ensure a system will meet its objectives. E.g are requirements being defined at the proper level of detail.

Quality Control: A set of activities designed to evaluate a developed work product. E.g. are the defined requirements the right requirements.

Testing: The process of executing a system with the intent of finding defects. (Note that the "process of executing a system" includes test planning prior to the execution of the test cases.)

Most Frequently asked Questions in Unix...

1. Which command is used to run an interface?
Sh

2. How will you see the hidden file ?
Ls -a

3. What is the command used to set the date and timings …
Date

4. Some basic commands like copy, move,delete ?
Cp, mv, rm

5. Which command used to the go back to the home directory ….
cd..

6. Which command used to view the the current directory
PWD

7. How to unzip the files in Unix?
tar -cvf

8. How to find help for a specific Command?
Mount (Command)

9. How t ochange Password ?
Passwd

10. How to search a string from file?
grep

11. How to cahnge Permissions on a file?
chmod

12. What is the command for a calculator?
bc

What should be done after writing test case?

After writing testcase we should review it. Reviewing can be done by another Test engineer/Peer or test lead...Once got the result fix the review comments. After completion of writing test cases you need to review the cases for completeness and correctness to check whether every functionality is covered, then we have to wait for build and we have to exe the reviewed testcases....

Difference between client server testing and web server testing.

Web systems are one type of client/server. The client is the browser, the server is whatever is on the back end (database, proxy, mirror, etc). This differs from so-called “traditional” client/server in a few ways but both systems are a type of client/server. There is a certain client that connects via some protocol with a server (or set of servers).

Also understand that in a strict difference based on how the question is worded, “testing a Web server” specifically is simply testing the functionality and performance of the Web server itself. (For example, I might test if HTTP Keep-Alives are enabled and if that works. Or I might test if the logging feature is working. Or I might test certain filters, like ISAPI. Or I might test some general characteristics such as the load the server can take.) In the case of “client server testing”, as you have worded it, you might be doing the same general things to some other type of server, such as a database server. Also note that you can be testing the server directly, in some cases, and other times you can be testing it via the interaction of a client.

You can also test connectivity in both. (Anytime you have a client and a server there has to be connectivity between them or the system would be less than useful so far as I can see.) In the Web you are looking at HTTP protocols and perhaps FTP depending upon your site and if your server is configured for FTP connections as well as general TCP/IP concerns. In a “traditional” client/server you may be looking at sockets, Telnet, NNTP, etc.