Interview Questions Answers.ORG
Interviewer And Interviewee Guide
Interviews
Quizzes
Home
Quizzes
Interviews Basic Job Interviews:AbilitiesAbroad JobsActivistAmbitionAnalyticalAptitudeAptitude KnowledgeAssertivenessAuthority / DecisivenessBasic CommonBasic Salary RequirementsBehavioralBehavioral BasedBody LanguageBusiness intelligenceCandidate Selection CriteriaCareer StatementsCareers FutureCaseCitizenshipCommunication SkillsComputer BasicsComputer securityConfidence BuildingConflictCorporate CommunicationCreativeCreativityCurrent Affairs 2009Current Affairs 2010Current Affairs 2011Dangerous JobsDecision MakingDetail SkillsDeterminationDifficultDream JobEmployers To AskEntry LevelEthicsExitFace to FaceFailuresFlexibilityFollow UpFrequently AskedFreshers GraduateFunnyFunny QuotesFuture Career PlanningGeneral KnowledgeGeneral SkillsGood EmployeeGood LeaderGraduationGroupGroup DiscussionsHackingHandle StressHard WorkerHotel TourismHow to AnswerIllegalIncidentInitiativeInitiative WorkplaceInteresting CareerInterestsJobJob AttireJob AwarenessJob DemotionJob Follow Up LetterJob KnowledgeJob PerformanceJob ProtocolJob Search TacticsJob TipsJudgmentLearning SkillsLinkedIn RecommendationListening SkillsLogicalMannersMental AttitudeMid LifeMost Inspiring JobsMotivationNegotiate Pay RaiseNegotiation SkillsNo ExperienceNo Work ExperiencePanelPart Time ContractPatiencePay PackagePersonalPersonality TraitsPhonePlacement AssistancePost GraduatePotential EmployeePresent JobProblem SolvingProblem Solving SkillsProhibitedProjectsPuzzlesQuality On TimeQuantitativeQuantitative AptitudeRecession Proof JobReferencesResignationResume FormatResume HelpResume ObjectivesResume Skill SetSalarySalary NegotiationSecond InterviewSecond RoundSecretarySelf AssessmentSelf WorthinessSituationalSkypeStatics ProbabilityStrange JobsTargeted SelectionTeamworkTeamwork MotivationTechnology SkillsTeenTelephone OperatorTelephonicToughTraining AdviceTrickyTypicalUnusualVideoVisaWarm UpWeaknesses and StrengthsWork EthicsWork HistoryWorkplace FlexibilityWritten Skills
Copyright © 2018. All Rights Reserved
Aptitude Knowledge Interview Question:
The following is an extract from a fault log, write down any potential problems or omissions with this?
Submitted by: AdministratorPotential Problems/Omissions
.. No date on log as to when raised
.. No keywords (i.e. screen) so that searches can be performed preventing duplication of fault logs
.. No status of the log (opened/fixed/closed/cleared etc.)
.. No owner of the log. .. Has priority - but no severity (i.e. risk to the customer)
.. No version number of the system being tested - it is very likely that the testers are on a different version to development and that it was a fault but has been inadvertently fixed on this latest software
.. Query the priority of this log (should it be a 3?)
.. No actual error message on the log - this may give some clue to the developer about the nature of the fault
.. Response seems to be leading to a dialogue - if we are not careful this fault will never be fixed! Tester should talk to the developer rather than sending another message via the fault log.
.. The response by the developer points to another part of the system (security) - this may be an indication of developers trying to quickly close the issue without performing sufficient investigation. It could however be because the tester has not spent enough time documenting the problem.
Submitted by: Administrator
.. No date on log as to when raised
.. No keywords (i.e. screen) so that searches can be performed preventing duplication of fault logs
.. No status of the log (opened/fixed/closed/cleared etc.)
.. No owner of the log. .. Has priority - but no severity (i.e. risk to the customer)
.. No version number of the system being tested - it is very likely that the testers are on a different version to development and that it was a fault but has been inadvertently fixed on this latest software
.. Query the priority of this log (should it be a 3?)
.. No actual error message on the log - this may give some clue to the developer about the nature of the fault
.. Response seems to be leading to a dialogue - if we are not careful this fault will never be fixed! Tester should talk to the developer rather than sending another message via the fault log.
.. The response by the developer points to another part of the system (security) - this may be an indication of developers trying to quickly close the issue without performing sufficient investigation. It could however be because the tester has not spent enough time documenting the problem.
Submitted by: Administrator
Copyright 2007-2024 by Interview Questions Answers .ORG All Rights Reserved.
https://InterviewQuestionsAnswers.ORG.
https://InterviewQuestionsAnswers.ORG.