International Software Testing Qualifications Board (ISTQB)

{{Software Testing}}
The ISTQB (International Software Testing Qualifications Board) was founded in Edinburgh in November 2002. The [[EOQ]]-SG (European Organisation for Quality – Software Group) is the legal entity acting as the umbrella organization for the ISTQB.

The ISTQB is responsible for the international qualification scheme called "[[ISTQB Certified Tester]]". The qualifications are based on a [[syllabus]], and there is a hierarchy of qualifications and guidelines for accreditation and examination.

The ISTQB Foundation Level exam became aligned with the [[ISEB]] Foundation Exam as of [[2006-06-01]]. ISEB, established in 1967 is the world's leading issuer of Software Testing qualifications and offers courses in over 50 countries worldwide.

Currently ISTQB only have a Foundation level exam available for Software Testing, with progression routes available through ISEB's intermediate and practitioner certificates.

It is the ISTQB's role to support a single, universally accepted, international qualification scheme, aimed at software and system testing professionals, by providing the core syllabi and by setting guidelines for accreditation and examination for national boards.

The contents of each syllabus are taught as courses by training providers, which have been accredited by national boards. They are globally marketed under the brand name "ISTQB Certified Tester".

Each course is concluded by an examination covering the contents of the syllabus. After the examination, each successful participant receives the "ISTQB Certified Tester" certificate (or the local variant with the added "ISTQB compliant" logo).

The accreditation process and certification are regulated by accreditation and certification regulations of the national boards (e.g. ASTQB - the [[American Software Testing Qualifications Board]]) in their various valid versions.

== External links ==
* [http://www.istqb.org ISTQB Official Website]
* [http://www.iseb-exams.com/st ISEB Official Website]
* [http://www.istqb.org/downloads/syllabi/SyllabusFoundation.pdf Syllabus (Version 2007)]
* [http://www.astqb.org ASTQB - ISTQB in the U.S.]
* [http://www.sqtl.com Leading ISTQB Training provider organization in India]
* http://www.istqb.org/downloads/syllabi/CTAL_Syllabus_V_2007.pdf

WHAT IS HTTPS ?

A. HTTPS stands for Hypertext Transfer Protocol over Secure Socket Layer or HTTP over SSL. HTTPS encrypts and decrypts the page requests and page information between the client browser and the web server using a secure Socket Layer (SSL). HTTPS by default uses port 443 as opposed to the standard HTTP port of 80. URL's beginning with HTTPS indicate that the connection between client and browser is encrypted using SSL.

SSL transactions are negotiated by means of a key based encryption algorithm between the client and the server, this key is usually either 40 or 128 bits in strength (the higher the number of bits the more secure the transaction).

HTTPS should not be confused with S-HTTP, a security-enhanced version of HTTP. SSL and S-HTTP have very different designs and goals so it is possible to use the two protocols together. Whereas SSL is designed to establish a secure connection between two computers, S-HTTP is designed to send individual messages securely.
Both protocols have been submitted to the Internet Engineering Task Force (IETF) for approval as a standard.

What is Secure Socket Layer (SSL)?

A. Originally developed by Netscape, SSL - short for Secure Sockets Layer - has been universally accepted on the World Wide Web for authenticated and encrypted communication between clients and servers. SSL works by using a public key to encrypt data that's transferred over the SSL connection.
The Transmission Control Protocol/Internet Protocol (TCP/IP) controls and is responsible for the routing and transmission of data all over the Internet. The SSL protocol runs in a "layer" above TCP/IP and below higher-level protocols such as HTTP or IMAP. SSL allows an SSL enabled server to authenticate itself to an SSL enabled client and vice versa enabling both machines to establish an encrypted connection .

SSL makes use of a public key infrastructure (PKI) to operate. The server operating securely generally obtains an SSL key and certificate pair from an issuing authority. It then makes these available on the server itself and announces the availability within the protocol exchanges between the server and client.
An SSL exchange is initiated with an SSL handshake where the client and the server exchange information with each other regarding the encryption information indicated by the SSL certificate.

Once this handshake is completed both the client and the server know exactly how to encrypt the information in a way that the other end will understand and be able to decrypt.
From that point on, anyone listening to (or snooping on) the data transfer between the client and the server will only see this encrypted information. They would then have to spend a long time decrypting it before they could make any sense out of it.

The greater the number of bits used when generating a certificate the stronger the encryption used with 1024 bit keys now being commonplace. It can take weeks of work using fast computers to successfully decrypt such a key. SSL encryption is available on web pages to a secure server. Further, messaging servers (such as

GMS) can also support SSL over POP3, IMAP4, SMTP as well as HTTP. By providing a complete secure route for messages, users of GMS can be confident that they can read, write and respond to email without anyone snooping on them.

SSL has more recently become known as Transport Layer Security, or TLS for short.

QA Testing

1.What is Software Testing?

A. Testing involves operation of a system or application under controlled conditions and evaluating the results, the controlled conditions should include both normal and abnormal conditions.Testing is a process of executing a program with the intend of finding the errors.

2. What is the Purpose of Testing?

A. The purpose of testing is

1· to uncover hidden errors

2· to achieve the maximum usability of the system

3· to Demonstrate expected performance of the system

3. What types of testing do testers perform?

A. Two types of testing 1.Functional testing 2. Non functional testing.

4. What is the Outcome of Testing?

A. The outcome of testing will be a stable application which meets the customer Req's

.5. What kind of testing have you done?

A. Usability, Functionality, System testing, regression testing, and AUT (it depends on the person).

6. What is the need for testing?

A. The Primary need is to match requirements get satisfied with the functionality

7. What are the entry criteria for Functionality and Performance testing?

A. Entry criteria for Functionality testing is Functional Specification /BRS (CRS)/User Manual. An integrated application, Stable for testing.Entry criteria for Performance testing is successfully of functional testing, once all the requirements related to functional are covered and tested, and approved or validated

8. Why do you go for White box testing, when Black box testing is available?

A. A benchmark that certifies Commercial (Business) aspects and also functional (technical) aspects is objectives of black box testing. Here loops, structures, arrays, conditions, files, etc are very micro level but they arc Basement for any application, So White box takes these things in Macro level and test these thingsEven though Black box testing is available, we should go for White box testing also, to check the correctness of code and for integrating the modules.

9. What are the entry criteria for Automation testing?

A. Application should be stable. Clear Design and Flow of the application is needed.

10. What is testing?
A. “The execution of an application manually with intention of finding errors.

11. When to start and Stop Testing?

A. This can be difficult to determine. Many modern software applications are so complex, and run in such an interdependent environment, that complete testing can never be done. Common factors in deciding when to stop are: Deadlines (release deadlines, testing deadlines, etc.) Test cases completed with certain percentage passed Test budget depleted Coverage of code/functionality/requirements reaches a specified point Bug rate falls below a certain level Beta or alpha testing period ends

12.What is Quality?

A. It ensures that software is a Bug free, delivered in time, with in budget, meets customer requirements and maintainable. Quality standards are different in various areas like accounting department might define quality in terms of Profit.

13. What is Baseline document?

A. The review and approved document is called as baseline document (i.e.) Test plan, SRS

14. What is verification?

A. To check whether we are developing the right product according to the customerrequirements and company standards r not. It is a static process.

15. What is validation?

A. Validation is a process of evaluating system or components at end of the development process to determine whether it is satisfies specified req. r not. It is a Dynamic process.

16. What is quality assurance?

A. Quality Assurance measures the quality of processes used to create a quality product.1. It is a system of management activities.2. It is a preventive process.3. It applies for entire life cycle.4. Deals with Process.

17. What is quality control?

A. Quality control measures the quality of a product1. It is a specific part of the QA procedure.2. It is a corrective process.3. It applies for particular product.4. Deals with the product.

18. What is SDLC and TDLC?

A. Software development life cycle (SDLC) is life cycle of a project from starting to ending of the project.1. Requiremnts Specification. 2. Analysis3.Design 4.Coding5.Testing 6.Delivery & Maintenance.Software Test Life Cycle (STLC) is a life cycle of the testing process.1. Test Initiation. 2. Test Planning3. Test case Design. 4. Review 5.Test case Execution6. Bug Reporting. 7. Test Closer

19.What are the Qualities of a Tester?

A. Tester should have qualities like 1. Ability to break 2.paitence 3.communication 4. Presentation 5.team work. 6. Negative thinking with good judgment skills

20.What are the various levels of testing?

A. The various levels of testing like1· Unit level testing2. Module Level testing 3. Integration level Testing4. System level testing5· UAT Level Testing

21.What are the types of testing you know and you experienced?

A. I am experienced in Black Box testing.

22. After completing testing, what would you deliver to the client?

A. It is depend upon what you have specified in the test plan document.The contents delivers to the clients is nothing but Test Deliverables.1. Test plan document 2.Master test case document 3.Test summary Report.4. Defect Reports.

23. What is a Test Bed? & Harness?

A. List of test cases to be executed is test bed. Harness means ready to start testing. Test harness =Test bed + Test Environment (test bed= list of test cases. Test environment = S/W+H/W).

24. Why do you go for Test Bed?

A. We will prepare test bed bcoz first we need to identify under which environment (Hardware, software) the application will run smoothly, thenonly we can run the application smoothly without any intereptions.

25. What is Severity and Priority and who will decide what?

A. Severity and priority will be assigned for a particular bug to know the importance of the bug. Tester can decide the severity and priority.Severity: How severely the bug is effecting the application.Priority: Informing to the developer which bug to be fix first.

26. Can Automation testing replace manual testing? If it so, how?

A. Yes, it can be done manually when the project is small, having more time.We can test with minimum number of users.

27. What is a test case?

A. A test case is a document that describes an input, action, or event and an expected response, to determine if a feature of an application is working correctly.
(Or)
It is a perception of test engineer to validate a specific functionality is called test case. It is one of the out coming document, it is a unique condition. In the testing phase to validate functionality a test engineer can take a several real time scenarios both positive and negative.

28. What is a test condition?

A. The condition required to test a feature. (Pre condition) Test condition derived from requirement specifications. It includes all possible combinations and validations

29.What is the test script?

A. Test script is the script which is generated by an automation tool while recording an application features. It contains navigations steps, Instructions, data exp, result……. To execute the test case

30. What is the test data?

A. Test data means the input data (valid, invalid data) giving to check the feature of an application is working correctly.

31. What is an Inconsistent bug?

A. The bug which is occurring.The bug which can’t catch even if we follow a process. It may occur, May not occur when we follow same scenario

32. What is the difference between Re-testing and Regression testing?

A. Re-testing: Testing the already tested application in the given AUT. In order to check the reproduceble of defect and role out the environmental issues.
Regression testing: Testing the already tested functionalities in the given AUT. Whether the already tested functionalities are changed or remain same because of newly added functionality to the application.

33. What are the different types of testing techniques?

A. 1. BVA (Boundary Value Analysis) 2. ECP (Equalence class partitiency) 3. Error Guessing

34. What are the different types of test case techniques?

A. 1. Equilance Partition. 2. Boundary Value Analysis. 3. Error guessing.

35. Differentiate Test bed and Test Environment?

A. Both are same. But little bit difference is there test bed is nothing but list of test cases to excuted. Test environment means S/W+ H/W.

36. What ifs the difference between defect, error, bug, failure, fault?

A. Defect: Deviation from desired functionality (Detected by test engineer- accepted by developer.)
Error: Mistake in coding (Un desirable deviation from requirements)Bug: Missing functionality / wrong functionality / Extra un wanted functionality
Failure: Absence of expected result (Client side people can find the mistake)
Fault: A Problem, which causes the system not to perform its task.

37. What is the difference between quality and testing?

A. QA is more a preventive thing, ensuring quality in the company and therefore the product rather than just testing the product for software bugs?TESTING means "quality control"Quality control measures the quality of a product.Quality Assurance measures the quality of processes used to create a quality product.

38. What is the difference between White & Black Box Testing?

A. White Box Testing: Based on the knowledge of the internal logic of an application's code. Tests are based on coverage of code statements, branches, paths, conditions. Black Box testing: - Not based on any knowledge of internal design or code.Tests are based on requirements and functionality. (It is a build level testing, to validate the customer requirements and an expectation depends on external interface).

39. What is the difference between Quality Assurance and Quality Control?

A. Refer Question no.16 & 17Quality Assurance measures the quality of processes used to create a quality product.Quality control measures the quality of the product.

40. What is the difference between Testing and debugging?

A. The Purpose of testing is to show the program has bugs.The Purpose of debugging is find the error/ misconception that led to failure and implement program changes that correct the error.

41. What is the difference between bug and defect?

A. Defect: While executing the test case if u found any mismatch, that u will report it to the development team that is called defect. Deviation from desired functionality (Detected by test engineer- accepted by developer.)Bug: Missing functionality / wrong functionality

42. What is the difference between verification and validation?

A. Verification: To check whether we are developing the right product according to the customer requirements and company standards are not. It is a static process.
Validation: Validations is a process of evaluating system or components at end of the development process, to determine whether it is satisfies specified requirement r not. It is a Dynamic process.

43. What is the difference between unit testing and integration testing?

A. Unit Testing: It is a testing activity typically done by the developers not by testers, as it requires detailed knowledge of the internal program design and code. Not always easily done unless the application has a well-designed architecture with tight code.Integration testing: testing of combined parts of an application to determine if they function together correctly. (Functionality flow of navigation) The 'parts' can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.

44. What is the diff between Volume & Load?

A. Combination of Load, volume and stress testing comes under performance testing.Load Testing: To test the performance of the application by gradually increasing the user loads.Stress Testing: TO test the performance of the application and to find the server break down or where the server crashes.Volume Testing: To test whether it can able to send max data according to client req's.

45. What is diff between Volume & Stress?

A. Stress Testing: TO test the performance of the application and to find the server break down or where the server crashes.Volume Testing: To test whether it can able to send max data according to client req's.

46. What is the diff between Stress & Load Testing?

A. Load Testing: To test the performance of the application by gradually increasing the user loads.Stress Testing: TO test the performance of the application and to find the server break down or where the server crashes.

47. What is the Diff between Two Tier & Three tier Architecture?

A. Two Tier Architecture: It is nothing but client server Architecture, where client will hit request directly to server and client will get response directly from server.Three tier Architecture: It is nothing but Web Based application, here in between client and server middle ware will be there, if client hits a request it will go to the middle ware and middle ware will send to server and vise-versa.

48. What is the diff between Integration & System Testing?

A. Integration testing: testing of combined parts of an application to determine if they function together correctly. The 'parts' can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.System Testing: system testing will conducted on the entire system to check whether it is meeting the customer requirements r not. (Or)
Testing the application as a whole from login to logout, to covering by all requirements with functionality end to end, interms of Usability, Functionality, and Non-functionality is System testing.

49. What is the diff between walk through and inspection?

A. Walk through: A 'walk through' is an informal meeting for evaluation or informational purposes. Little or no preparation is usually requiredInspection: Inspection is an formal meeting, here every thing discussed will be documented such as a requirements spec or a test plan, and the purpose is to find problems and see what's missing, The result of the inspection meeting should be a written report.

50. What is the Diff between static and dynamic?

A. Static Testing: Test activities that are performed without running the software is called Static Testing, it includes inspections, walk throughs and desk checks.Dynamic testing: Test activities that are performed by running the software is called dynamic Testing.

51. What is the diff between alpha testing and beta testing?

A. Alpha Testing: Alpha testing will be performed by in the presence of client in our environment with dummy data, in this phase some major bugs can be allowed, later which will be solved by our development team.Beta testing: Beta testing will be performed by client in his environment with real data.

52. What is the diff between Client Server & Web Based Testing?

A. Client server application is 2 tier applications and web Application is n tier application.Client server is the single user application and the web Application is the multi User .

53. What is functional testing?

A. It is mandatory level in Block box testing, validating the functionality of the application according to business requirements, to check the behavior of the application. Functional testing main object is “To meet customer requirements”. It is also known as ‘Requirements testing’, test engineers validates the correctness of functionalities in terms below coverage’s.1. Whether it is taking valid text data or not.2. If it is taking valid data, it is giving correct output or not3. If we are giving invalid data whether it shows error messages or not4. It is preventing wrong (negative) navigations or not5. Impact of front operations on backend tables contents6. Order of functionalities.

54. What are the risks involved in the testing?

A. 1.Resource risk A. Human Risk B. H/W risks C. S/W risks 2. Technical Risks 3. Commercial RisksRisks involved in testing process 7 types……1. Lack of time2. Lack of knowledge3. Lack of resources4. Lack of documents5. Lack of communication6. Lack of seriousness7. Lack of deliverables.

55. What is mean by UAT?

A. If we perform every test as user acceptance test, after completion of all possible functional system tests, our organization management is concentrate on UAT. The main object is “Feed back from customer side people”. AT is done to achieve the following1. User specified requirements have been satisfied2. Functionality is doing as per supporting documents3. Expected performance have been achieved4. End user is comfortable to use the application
UAT 2 types
Alpha Testing: In the presence of client our environment is called alpha testing
Beta testing: In the presence client and his environment our people can do testing is called beta testing.

56. What is traceability matrix?
A. It is an inner mapping between requirement id to defect id via test case id. This is gives a summary report on that total testing process. It is a brief conclusion of testing process, quality can be measured by using trace matrix. Trace matrix has been maintained to ensure that verification & validation of the testing is complete.

57. What is SRS Documents contains? What’s its use?
A. It defines the complete behavior of the system to be build.
Bridge between customer and company.
1.INTRODUCTION
a .purpose
b.context diagrams
c.scope
d.functional de composition diagrams
e.definitions & acronyms
f.system functions
g.references & Major constraints

2.FUNCTIONAL REQUIREMENTS
a.database requirements
b.UI req
c.computability req
d.reports req

severity req
i
system features
j
traceability matrix

3
NON FUNCTIONAL REQ
4
COMMON CONSIDERATIONS
a
performance req
a
External interface specifications
b
safety req
b
user interfaces
c
security req
c
hardware interfaces
d
software quality attributes
d
software interfaces
e
business rules/other req
e
communication interfaces


58. What is the advantage of test case documents?
A. 1. Proper testing can be done.
2. We can validate the application in all possible permutation and combination.
3. Without repeating, without missing the tasks we can do the testing.
4. Any feature changes occur we can modify the test case document.
5. It makes us to follow a democratic approach
6. It useful for feature correspondence.
7. We can measure how many requirements covered.
8. At what level the quality is coming out.
9. The defect severities and prioritized in easy manner.
10. Correspondence will be developed to customer, tester, and developer also.

59. What is negative testing?
A. We test the application in all perspective. What is the application is not suppose to do. We give the invalid data for negative testing.

60. What is smoke and Sanity testing?
A. Smoke: Whenever we received the initial build from the developer we check whether all fields are available in every screen or not? And also we check the stability of the application.
Sanity: All fields are available ok but that fields are testable are not? Ex: Edit box is there editable or not. List box there list out all items or not?

61. What are the challenges you faced while you testing?
A. 1. Avoiding the duplication of testing effort across the different phases of testing
2. Reduce the cycle time of testing.
3. Standard testing process, templates and methodologies
4. Maintaining objectivity in the testing process
5. Availability of test environmental trained resources
6. Involvement testing in the entire system life cycle
7. Communication with development team
8. Unstable work package & environment
9. Shared Environment
10. Lack of dedicated environment support
11. Short time frames
12. Co-ordination with other team
13. Access from offshore for environment setup
14. Slow response
15. Knowledge acquisition due to various sub systems

62. What us usability testing?
A. Test execution process starts with usability testing. We are looking for the user friendliness of the application. This testing main object is “User friendliness”. A common user can use the application without any hesitation. Instructions should be available on every screen.
1. Ease of use: Understandable screens
2. Look & Feel: Attractiveness or pleasantness of screens
3. Speed in interface: Less number of events to complete a task
4. Context sensitiveness of user commands
5. Help documents.
6. Meta data (Tool tips).

63. What is BVA and ECP?
A. BVA: Identifying the boundary conditions of an object with in a given range of inputs.
ECP: Dividing the input domain in to valid and invalid types according to the business usage of the application.

What are some recent major computer system failures caused by software bugs?

In April of 2003 it was announced that the largest student loan company in the U.S. made a software error in calculating the monthly payments on 800,000 loans. Although borrowers were to be notified of an increase in their required payments, the company will still reportedly lose $8 million in interest. The error was uncovered when borrowers began reporting inconsistencies in their bills.

News reports in February of 2003 revealed that the U.S. Treasury Department mailed 50,000 Social Security checks without any beneficiary names. A spokesperson indicated that the missing names were due to an error in a software change. Replacement checks were subsequently mailed out with the problem corrected, and recipients were then able to cash their Social Security checks.

In March of 2002 it was reported that software bugs in Britain's national tax system resulted in more than100,000 erroneous tax overcharges. The problem was partly attributed to the difficulty of testing the integration of multiple systems.

A newspaper columnist reported in July 2001 that a serious flaw was found in off-the-shelf software that had long been used in systems for tracking certain U.S. nuclear materials. The same software had been recently donated to another country to be used in tracking their own nuclear materials, and it was not until scientists in that country discovered the problem, and shared the information, that U.S. officials became aware of the problems. According to newspaper stories in mid-2001, a major systems development contractor was fired and sued over problems with a large retirement plan management system. According to the reports, the client claimed that system deliveries were late, the software had excessive defects, and it caused other systems to crash.

In January of 2001 newspapers reported that a major European railroad was hit by the aftereffects of the Y2K bug. The company found that many of their newer trains would not run due to their inability to recognize the date '31/12/2000'; the trains were started by altering the control system's date settings. News reports in September of 2000 told of a software vendor settling a lawsuit with a large mortgage lender; the vendor had reportedly delivered an online mortgage processing system that did not meet specifications, was delivered late, and didn't work.

In early 2000, major problems were reported with a new computer system in a large suburban U.S. public school district with 100,000+ students; problems included 10,000 erroneous report cards and students left stranded by failed class registration systems; the district's CIO was fired. The school district decided to reinstate it's original 25-year old system for at least a year until the bugs were worked out of the new system by the software vendors.
In October of 1999 the $125 million NASA Mars Climate Orbiter spacecraft was believed to be lost in space due to a simple data conversion error. It was determined that spacecraft software used certain data in English units that should have been in metric units. Among other tasks, the orbiter was to serve as a communications relay for the Mars Polar Lander mission, which failed for unknown reasons in December 1999. Several investigating panels were convened to determine the process failures that allowed the error to go undetected.

Bugs in software supporting a large commercial high-speed data network affected 70,000 business customers over a period of 8 days in August of 1999. Among those affected was the electronic trading system of the largest U.S. futures exchange, which was shut down for most of a week as a result of the outages.In April of 1999 a software bug caused the failure of a $1.2 billion military satellite launch, the costliest unmanned accident in the history of Cape Canaveral launches. The failure was the latest in a string of launch failures, triggering a complete military and industry review of U.S. space launch programs, including software integration and testing processes. Congressional oversight hearings were requested.

A small town in Illinois received an unusually large monthly electric bill of $7 million in March of 1999.This was about 700 times larger than its normal bill. It turned out to be due to bugs in new software that had been purchased by the local power company to deal with Y2K software issues.

Chief Resume elements, you shouldn't skip!

A potential resume accentuates your achievements, your wok experience and educational qualifications along side escalating your expertise and dynamism. In today's competitive world, even the best of educational qualification will not get you the job; you will have to persuade the recruiter during the interview. Your resume is a declaration of facts intended to highlight your exceptional combination of comprehension & talent to convince your employer.
Academic qualifications can build a striking resume. List them in reverse sequence, i.e., from most recent to least resent. If you are doing some part time or specialization at present, highlight it. Stating the year of graduation and post graduation is wise.

Accentuate your achievements. For successfully getting an interview call highlight all the reasons why must he call you in? It is your résumé's crisp, attractive information that will persuade recruiter to call you for the interview. It's the section to openly say why you are the best contender for this job!State individually the Summer Training, Work Shops, Corporate Projects under taken. You must emphasize on all the areas clearly. Don't mix them under one heading. Remember you will not assist the reader. He will read just as you have written. They will give you an edge if set correctly.

Glorifying your co-curricular achievements is a good step. This is one section where we must know how to restrict the information we are providing. Just don't list all the little debate competitions you have attended. Just mention the prestigious ones where you have scored a good position. It can be in sports, arts, etc. this section will depict you as an all-rounder. When called for interview, remember carrying along all your certificates of achievement.

References will back bone your resume. Someone senior from the same organization or your previous job can refer you for the job. This section will give your recruiter a chance to find about you. Make sure you give the correct contact no. of the person(s) you are naming under reference section.

Providing correct Contact Information is a must. Contact Information will allow your recruiter to contact you for further after going through your resume. So must give correct and complete postal mailing address, e-mail address, permanent residence phone number, your mobile phone number, etc. Don't change mobile phone numbers during this time. And keep checking your e- mails regularly.

Remember there is no worth of a general resume any more. The jobs today are specific and so must the résumé's be. Make sure your resume is altered according to requirements of the job you are seeking.This is the first step for getting an interview call!

Foolish mistakes that Job seekers make in an Interview

Arriving LateWalking in for the interview even ten minutes after the interview is scheduled for, sends a negative first impression to potential employers. Get detailed directions to the interview site and calculate how long it will take you to get there, so that you can arrive 10 minutes early.

Inappropriate AppearanceImproper clothes and grooming can jeopardize an interview. Casual clothes are definitely out. Your objective should be to dress smartly and not overtly. Remember, nails should be cut, hair well groomed and shoes polished. These may seem like little things but they count for a lot in any interview.

Poor Communication SkillsA candidate who has bad grammar, talks too much, or does not listen is a red flag. Being too open during the interview is a killer too. You should be candid, but don’t pile the interviewer with all of your personal problems. Think before you speak!!

Poor Performance or PreparationYes, there are job seekers who don’t prepare for the interview or even know what job they are interviewing for. Lack of eye contact, extreme gestures or movements, and other physical ticks can really turn off employers.
Negative Attitude DisplayHiring managers are turned off by unenthusiastic, bored or arrogant behavior. Using profanity, acting cocky, or putting down a previous boss will quickly turn off an interviewer.

Lying in the Resume or During InterviewDo you have to told that dishonesty is a no-no? For example, do not falsely claim to have earned degrees or certificates and do not cover up a possible criminal record. Also, just in case you weren’t sure, stealing from a prospective employer is also frowned upon in an interview.Failing to Confirm Interest After the employer has finished explaining the details of the organization and the job description, it is your responsibility to reaffirm your interest and ask what the next step is.