INTERVIEW QUESTIONS Flashcards
HOW WOULD YOU DESCRIBE YOURSELF?
I AM A GRADUATE OF COLUMBIA UNIVERSITY’S SOFTWARE DEVELOPMENT PROGRAM. SOON AFTER GRADUATING I BEGAN AN INTERNSHIP AT A COMPANY CALLED TUNECORE WHERE I EXCELLED AND WAS OFFERED A FULL TIME JOB. SOMETIME LATER HOWEVER I BECAME MORE INTERESTED IN QA SO I MADE THE SWITCH. SINCE I HAVE A COUPLE YEARS AS A TESTER WITH HANDS ON TESTING OF BUSINESS SYSTEMS. I HAVE WORKED CLOSELY WITH THE QA MANAGER, BA’S, PROJECT MANAGERS, AND DEVELOPERS. I HAVE EXPERIENCE CREATING TEST DOCUMENTS SUCH AS TEST PLANS, TEST SCENARIOS, TEST CASES RTM AND ASSISTING WITH THE UAT PLAN. I HAVE IN DEPTH KNOWLEDGE OF THE SDLC, STLC, AND DLC. I AM EAGER TO TAKE ON CHALLENGES AND CONTRIBUTE TO THE SUCCESS OF THE TEAM AND PROJECT.
EXPLAIN THE SDLC
THE SDLC IS THE MOST COMMONLY FOLLOWED PROCESS OF ANY SOFTWARE PROJECT. IT SPECIFIES AN APPROACH FOR DEVELOPING SOFTWARE IN STAGES. AND THOSE STAGES BEGIN WITH PLANNING.
IN THE PLANNING STAGE THIS IS WHERE YOU DEFINE THE SCOPE OF A PROJECT, SET THE OBJECTIVES AND GOALS AND RESOURCE PLANNING TAKES PLACE. STUDIES AND RESEARCH ARE PERFORMED TO HELP THE COMPANY DETERMINE IF THEIR MISSION IS FEASIBLE . GETTING TO KNOW YOUR CUSTOMER, YOUR COMPETITION, AND MARKET.
NEXT YOU HAVE THE REQUIREMENTS ANALYSIS STAGE WHERE THAT INCLUDES GATHERING, ANALYZING, VALIDATING, AND SPECIFYING REQUIREMENTS AND THIS IS WHERRE THE SRS IS CREATED.
ONCE COMPLETE WE CAN MOVE ON TO DESIGNING STAGE WHERE WE USE THE SRS AS A REFERENCE FOR SOFTWARE DESIGNERS TO COME UP WITH THE BEST ARCHITECTURE FOR THE SOFTWARE.
FROM THERE WE MOVE ON TO WHERE THE ACTUAL CODING TAKES PLACE WHICH IS DONE BY THE DEVELOPMENT TEAM.
AFTER DEVELOPMENT, THE CODE GOES THROUGH THE TESTING AND INTEGRATION PROCESS WHERE THE CODE IS TESTED AND MAPPED AGAINST THE DESIGN DOCUMENT AND DESIGN PHASE.
AND FINALLY DEPLOYMENT AND MAINTENANCE.
EXPLAIN THE BUG LIFE CYCLE (BLC OR DLC)
MANAGEMENT IS A VITAL PHASE OF THE SOFTWARE TESTING LIFECYCLE. AS A QA IT HAS BEEN AN INTEGRAL PART OF THE TESTING PROCESS IN MOST OF MY PROJECTS.
WHEN AN ERROR IS FOUND THE STATUS IS SET TO NEW AND THEN ASSIGNED TO A DEVELOPER. AFTER BEING ASSIGNED A DEV CAN EITHER ACCEPT OR REJECT THE BUG OR DEFER IT . IF ACCEPTED THE DEVELOPER WILL WORK ON IT AND THE BUG WILL BE IN PROCESS AND THEN EVENTUALLY FIXED. ONCE FIXED WE RETEST AND VERIFY THAT IT HAS INDEED BEEN FIXED AND IF IT HAS WE CAN CLOSE IT OUT. IF THE ISSUE IS STILL THERE THE BUG GETS REOPENED AND ASSIGNED BACK TO A DEVELOPER AND STARTS THE PROCESS OVER AGAIN.
WHAT ARE THE DIFFERENT DOCUMENTS A QA PREPARES
OVER THE YEARS WORKING AS A QA IVE BEEN INVOLVED IN PREPARING TEST STRATEGY’S, TEST PLANS, TEST SCENARIOS, TEST CASES, RTMS, DAILY/WEEKLY REPORTS, BUG REPORTS, TEST CLOSURE REPORTS.
WHAT DIFFERENT ARTIFACTS DO YOU REFER TO WHEN YOU WRITE TEST CASES?
THE MAIN ARTIFACTS I REFER TO AS A QA ARE THE
BUSINESS REQUIREMENTS DOCUMENT - BRD
FUNCTIONAL REQUIREMENTS SPECIFICATIONS - FRS
SYSTEMS REQUIREMENTS SPECIFICATION - SRS
USE CASES
WIREFRAMES
HIGH LEVEL DESIGN DOCUMENT
WHAT IS A USE CASE TESTING
A USE CASE IS A INTERACTION BETWEEN A USER AND A SYSTEM. ITS A GREAT WAY TO PAINT A PICTURE OF HOW A USER INTERACTION SHOULD BASED ON FUNCTIONAL REQUIREMENTS.
WHAT IS A TEST STRATEGY DOCUMENT AND IT’S COMPONENTS?
A TEST STRATEGY IS THE HIGHEST DOCUMENT IN THE STLC HIERARCHY. IT IS USUALLY DEVELOPED BY A TEST MANAGER/LEAD. IT DEFINES THE SOFTWARE TESTING APPROACH AND SCOPE OF THE PROJECT.
THE PROJECTS WHAT, WHEN, WHERE, WHY, AND WHO.
THE PURPOSE, OBJECTIVE, TEST ENVIRONMENTS, TOOLS.
WHAT IS A TEST PLAN AND WHAT ARE THE DIFFERENT COMPONENTS?
A TEST PLAN IS THE SECOND HIGHEST DOCUMENT IN THE SLDC HIERARCHY. CREATED BY THE TEST LEAD. DETAILS OBJECTIVES, RESOURCES, AND PROCESSES FOLLOWED FOR A SOFTWARE SYSTEM. FOCUES ON THE HOW AND WHY.IT DISCUSSES THE FEATURES TO BE TESTED, THE ROLES AND RESPONSIBILITIES, TYPES OF TESTING AND TEST DELIVERABLES.
WHAT IS A TEST CASE AND THE DIFFERENT COMPONENTS OF IT?
A TEST CASE DESCRIBES THE INPUT, ACTIONS, AND EXPECTED RESPONSES, TO DETERMINE IF THE SYSTEM IS WORKING PROPERLY. A TEST CASE WILL INCLUDE:
A TITLE
A UNIQUE ID
PRE-CONDITIONS
STEPS TO REPRODUCE
DESCRIPTION
EXPECTED RESULTS
ACTUAL RESULTS
STATUS (PASS OR FAIL)
WHAT IS THE REQUIREMENTS TRACEABILITY MATRIX RTM AND HOW CAN IT BE USEFUL?
THE RTM IN ANY SOFTWARE DEVELOPMENT PROJECT IS AN INTEGRAL PART OF THE TEST DOCUMENTATION. ITS A DOCUMENT THE HELPS KEEP TRACK AND MAP ALL THE REQUIREMENTS TO THEIR RESPECTIVE TEST CASES AND ENSURE 100% THAT EVERYTHING IS BEING COVERED IN THE TEST PHASE.
WHAT IS THE DIFFERENCE BETWEEN VERIFICATION AND VALIDATION?
IN SHORT VERIFICATION IS VERIFYING THAT THE SYSTEM IS EING BUILT CORRECTLY. HELPS WHETHER THE GIVEN PRODUCT SATISFIES THE SPECIFIED REQUIREMENTS.
VALIDATION IS VALIDATING YOU’RE BUILDING THE RIGHT SYSTEM. IT’S CHECKING TO MAKE SURE IT’S MEETING THE CUSTOMER REQUIREMENTS.
EXPLAIN THE TESTING LEVELS OR TYPES OF TESTING
THERE ARE FOUR LEVELS OF TESTING.
UNIT TESTING:
IS THE TESTING OF INDIVIDUAL UNITS OR COMPONENTS DONE BY DEVELOPERS TO TEST THAT THE UNIT THEY’VE IMPLEMENTED IS PRODUCING AN EXPECTED RESULT.
INTEGRATION TESTING:
IS A LEVEL OF TESTING THAT WHEN NEW FEATURES ARE BEING INTRODUCED TO THE SYSTEM EVERYTHING WORKS AS IT SHOULD WHEN COMBINED. THE INTERACTION BETWEEN SOFTWARE AND HARDWARE IS TESTED IN INTEGRATION AS WELL
SYSTEM TESTING:
IS DONE BY TESTERS AND IT IS TO TEST THAT WHEN THE SYSTEM IS GIVEN AN INPUT IT SHOULD RESPOND THE WAY IT IS SUPPOSED TO
ACCEPTANCE TESTING:
IS THE END USERS TESTING.
EXPLAIN AGILE METHODOLOGY
AGILE IS A METHODOLOGY OF SOFTWARE DEVELOPMENT THAT SUPPORTS RAPID COLLABORATION BETWEEN TEAMS, PROMOTES ADAPTIVE PLANNING, AND FOCUSES ON QUALITY-DRIVEN SOLUTIONS THROUGH CONTINUOUS IMPROVEMENT.
EXPLAIN THE DIFFERENT TYPES OF SOFTWARE TESTING
SOFTWARE TESTING CAN BE DIVIDED INTO TWO TYPES, STATIC AND DYNAMIC.
STATIC TESTING IS A TECHNIQUE USED TO PROVIDE AN ASSESSMENT OF DOCUMENTATION BY FINDING AND ELIMINATING ERRORS OR AMBIGUITIES IN DOCUMENTS SUCH AS REQUIREMENTS, DESIGN, TEST CASES ETC.
DYNAMIC TESTING IS FURTHER DIVIDED INTO TWO TYPES, FUNCTIONAL AND NON FUNCTIONAL.
FUNCTIONAL TESTING IS TESTING THE LOGIC BEHIND AN APPLICATION AND CHECKING TO SEE IF THEY WORK PROPERLY WITH THE REQUIREMENTS.
NON FUNCTIONAL TESTING THE NON FUNCTIONAL REQUIREMENTS OF A SYSTEM, FOR EXAMPLE THE PERFORMANCE, USABILITY, RELIABILITY, SECURITY ETC.
DEFINE SCRUM
SCRUM IS THE MOST WIDELY USED AGILE METHODOLOGY FRAMEWORK. THE THREE KEY ROLES OF SCRUM ARE THE SCRUM MASTER, SCRUM TEAM, AND PRODUCT OWNER. FEATURES AND REQUIREMENTS ARE DIVIDED INTO SPRINTS WHICH ARE TWO WEEK LONG DEADLINES. AND YOU HAVE YOUR SCRUM MEETINGS WHICH AREA:
SPRINT PLANNING IS THE FIRST MEETING AND THE BEGINNING OF EACH SPRINT. THIS IS WHERE THE SCOPE OF THE WORK IS DETERMINED BY PLANNING AND REVIEWING SPRINT BACKLOG ITEMNS
DAILY STAND UP MEETINGS THAT COVER WHAT EACH INDIVIDUAL DID SINCE LAST MEETING, WHAT IS THE TASK FOR TODAY, AND ANY SOLUTIONS OR QUESTIONS TO ANY PROBLEMS ONE MAY BE HAVING.
SPRINT REVIEW IS A MEETING TO DISCUSS ACCOMPLISHMENTS, MILESTONES THROUGHOUT THE SPRINT.
AND THE SPRINT RETROSPECTIVE MEETING IS THE LAST MEETING AT THE END OF THE SPRINT DESIGNED TO COVER WHAT WENT WELL, WHAT COULD IMPROVE, AND AN OVERALL CONSTRUCTIVE CRITIQUE OF THE SPRINT AS A WHOLE.
