For any interview, the first thing to prepare is the resume. It creates an impression about you even before meeting you. Make it look neat, short and crisp. Do not leave the achievements column blank. Write a brief overview about your previous projects. Do not boast, but make diplomatic statements that will show that you are capable.
Next would be your appearance. Neatly pressed formal clothes would be mandatory for an interview. Be confident when you approach the interviewer. Never show your nervousness out. Be very honest when you answer the questions. Always be ready to say “I am not aware of this” when you don’t know something (But not for all the questions ofcourse! :)). Never give wrong answers. Listen carefully and understand the questions. Prepare well to talk all about your project and your role that you have stated in your resume. Do not say anything negative about your current employer. Be very clear with your concepts and never mess up with that.
Thursday, December 1, 2011
TCL Tutorial
If you are beginner in TCL and would like to teach yourself this simple language, you can do it using a tcl tutor. You need not buy expensive books or search the net for online materials to learn the language. All you have to do is, download tcl tutor from the below link and start working on it from the first chapter
https://tcltutor.software.informer.com/3.0/
TCL tutor is designed in such a way that you can learn concepts and keywords from the chapters listed in the tutor and at the same time execute them and look for the output. Sample code will be available in each chapter which can be executed and you can also write your own code and try to execute it and look for the output.
To start with, beginners can go through the tutor chapter by chapter and execute them and understand the concepts. Experienced programmers working on TCL projects can also use this tutor. You can go to the particular concept or keyword that you have problem with, and refer the tutorial. You can also copy paste your piece of code that you have an issue with and execute them in the tutor to find out the flow and locate your mistake. TCL is mostly used for automation testing and hence if you are stuck up with a particular line in the script due to syntax errors or any other issues, you can verify them using the tutor and then make changes accordingly and then go for the next execution, instead of running the whole script again to find another syntax error in some other line! This way it is a big gift for TCL programmers.
Some Useful Links To Refer Before Attending Software Testing Interviews
I found these links really useful for an interview (both as an interviewer and as an interviewee)
These links are with respect to software testing.
Testing Interview Questions And Answers
These are the answers to the "software testing" questions:-
1. Difference between black box and white box testing.
1. Difference between black box and white box testing.
Black box Testing:
Black box testing is the testing where the tester is unaware of the code and structures inside the application that is tested. The tester knows only the valid inputs supplied and the expected outputs corresponding to those inputs. If the expected result is not obtained, the tester files a bug.
White Box Testing:
White Box testing is one where the tester is aware of the internal code flow and structures and he tries to test if all the modules are hit properly when different inputs are supplied. In most cases developers perform the white box testing as they are aware of the modules they have created.
2. Who does white box testing(Developers or testers)?
Black box testing is performed by testers
White box testing is mostly performed by developers
3. Why the name 'black box' and 'white box' testing?
If we look at the application as a single box, in the case of black box testing, the tester is unaware of the code structures inside and hence the application looks like a black box to him with just the input going into it and the output that is expected to come out of it.
In the case of a white box testing, the tester (in fact the developer) knows the application in and out including the code structures. So the applications looks like a white transparent box to him, where he can see the modules in it and test if all the modules are hit properly and the code is optimized.
4. Is unit testing white box or black box?
Testing an individual module of an application is called unit testing.
Developers perform unit tests and therefore it comes under white box testing.
In white box testing the basic path coverage, loops and functions written in the code are tested
On the other hand, black box testing tests the functionality of an application
5. Difference between regression and re-testing?
Regression Testing
When we perform testing after making changes to the current build it is called regression testing. In other words regression testing is performed time and again on different builds to see if the code changes in the subsequent builds affect the output/functionality.
Retesting
On the other hand, when we perform testing time and again on the same build it is called retesting. Sometimes an application might behave in an inconsistent way giving different outputs when we retest. To capture such bugs we do retesting.
6. Why is testing essential for a project? What is the significance of testing?
Testing is an integral part of a project as it improves the quality of an application that is created. Any basic functionality that is left out during the development phase can be captured during the testing phase. A developer over looks certain issues as he does not want his code to break. But a tester's main aim is to break the application when a valid input is given, which means the application has a bug and needs to be fixed.
7. Name a bug that you had raised in your project that was appreciated?
Think of something that brought you several appreciation mails from clients. Something that the developer had really missed and if delivered as is, could have caused a big blow.
8. Difference between Verification and Validation testing is a very common question in any testing interview. I had faced this question time and again and was really very much interested to shoot it on the bull's eye. That is when I found these explanations from a site. I made a backup and it is available here
http://networkinterviewquestionsandanswers.blogspot.in/2012/08/excellent-explanation-for-difference.html
8. Difference between Verification and Validation testing is a very common question in any testing interview. I had faced this question time and again and was really very much interested to shoot it on the bull's eye. That is when I found these explanations from a site. I made a backup and it is available here
http://networkinterviewquestionsandanswers.blogspot.in/2012/08/excellent-explanation-for-difference.html
Subscribe to:
Posts (Atom)