DTD Interview Questions and Answers
We have listed of DTD Interview Questions and Answers that have been designed for DTD professionals who are preparing interviews on DTD. The document type definition (DTD) is a set of mark-up declarations that can be define document type for an SGML-family mark-up language (SGML, XML, HTML). A DTD defines the valid building blocks of an XML document. DTDs were originally part of SGML (Standard Generalized Markup Language) the ancestor of both HTML and XML. DTD is the most common schema language in use with XML documents.
Best DTD Interview Questions and Answers
Below we have provided best DTD Interview Questions that are specially designed for DTD Programmers.
What is Document Type Definition (DTD)?
DTD stands for document type definition. it describes elements that appear in the XIVIL document what are its contents and attributes Reply with Quote
Can QEngine test Java applets?
No. Currently, not supported.
What are Standards for Software Test Plans?
Several standards suggest what a test plan should contain, including the IEEE. The standards are: IEEE standards: 829-1983 IEEE Standard for Software Test Documentation 1008-1987 IEEE Standard for Software Unit Testing 1012-1986 IEEE Standard for Software Verification & Validation Plans 1059-1993 IEEE Guide for Software Verification & Validation Plans
What is test case analysis?
Test case analysis means reviewing the test case normally done by team lead or Quality Manager. In this process he / she walkthrough the test cases and compares with the SRS or functional document and also checks whether all major scenarios were considered by test engineer while writing the test case and informs accordingly.
What are the main things we have to keep in mind while writing?
The main focus while writing test cases should be to cover all the documented requirements, a rudimentary form of doing this is by specifying the exact requirement number/id against every test case. A better way of doing this is by preparing a Traceability Matrix We should also try and write which cover the implicit requirements along with the explicit stated ones, some negative test cases to cover unpredictable scenarios. Effort should be made to test all possible inputs and to apply whatever domain knowledge the tester has. The test cases should follow a logical flow, and should include all the information required for executing the steps.
What is the difference between UseCase and TestCase?
Difference between test case and use case is use case is prepared by High Level Management team but test case is prepared by Test engineers. Use case is prepared for validating the applications in terms of Actors, actions and responses but test case is used to test a specific functionality of an application.
What is installation shield in testing?
Install Shield is the software which is used to create the setup files. There is Installation testing which ensures that the user can install the software without any problem and the files are getting stored at proper place and all the register entry are getting stored properly. There is nothing called Installation Shield testing.
What are the management tools we have in testing?
There is no particular bug tracking tool. It will vary from company to company. In my company they are using Bugzilla. In some comp use TD, Service Point, manita1.0.1, Test Team, etc..
Can we write Functional test case based on only BRD or only Use case?
Yes, we can, but you cannot have a full flow on that test case. Because BRD and use cases used to prepare FRS.with help of FRS we can write our test case.
What is main difference between smoke and sanity testing? when these are performed? Explain with example?
sanity testing is also called as Build verification testing. Every Build release from developer should be followed by sanity testing. – In sanity testing we install the application, launch the application and navigate through the application. – Sanity test is implemented to make sure the application is ready for complete testing.
Every Build release to the client should be preceded by smoke testing. – smoke testing is implemented to make sure the application given to the client on the final release media is working fine, – smoke testing will be a quick test phase to test installation, launching and basic functionality navigation. – smoke testing is carried out using the check lists. -smoke testing is carried out before every release to the client.
What Technical Environments have you worked with?
According to me Technical environments depends on company to company and also on the compatibility of project like most of the projects supports Windows and 3 – tire application in case of Database or some s/w will work on Unix / Linux so answer for this will different for different users.
Define Bug Life Cycle? What is Metrics?
When we find out the bug, we will put into the “open” status. After fixing the bug developer change the status as “fixed”. Again we will test the fixed part, if there is no bug, change the bug status as “Closed” otherwise change the bug status as “Reopen”. A s/w metric defines a standard method of measuring certain attributes of the process or the product or the service.
What is a Test procedure?
Test Procedure is a part of Test Case document. It comprises of following three steps:
- To verify the look and feel of AUT through GUI test cases.
- To verify the positive behaviour of AUT through positive test cases.
- To verify the negative behaviour of the AUT through negative test cases.
What is the difference between SYSTEM TESTING and END-TO-END TESTING?
System testing is the phase of software testing in which the complete system is tested. It follows Integration testing. End to End testing is the testing of the application for all the possible scenarios. It is someway related to Exhaustive testing of the application. however, this cannot be done in practise as they are more time consuming.
What is Traceability Matrix? Is there any interchangeable term for Traceability Matrix?
I think it is not Matrix..it is Metrics.Traceability Metrics is a proof of document to ensure that all the specifications are been tested and the application is bug free.
Thus, the compilation of these questions includes some of the major points that can be asked during an interview. The DTD interviewers generally check the base knowledge of a candidate, which can be gained by practicing these questions prior interview.
So if you have finally found your dream job in document type definition (DTD) but are wondering how to crack the DTD Interview and what could be the probable DTD Interview Questions. Every interview is different and the scope of a job is different too. Hope above assist you to get a dream Job. Keep Learn.