In: Computer Science
Scenario Please read this scenario and job description carefully. You are involved in the prestigious but often challenging Google recruitment process. As part of this process you are required to respond to several questions and activities. All your answers must address the context of this scenario and the information given in the individual questions
. Job description - Software development professional at Google There's no such thing as “a normal day" at Google. We work to create and maintain the safest operating environment for Google's users and developers. Users come first at Google! As part of your work at Google, on any day you might be exposed to the full suite of Google products. You will be working on some exciting new products at Google, such as Google Digital Garage, our online learning platform. You will also be working across a growing Internet of Things (IoT) portfolio. You will also work as part of our Advertising and Commerce team: we believe that ads and commercial information can be highly useful to our users if that information is relevant to what our users wish to find or do. Advertisers worldwide use Google Ads to promote their products; publishers use AdSense to serve relevant ads on their website; and business around the world use our products (like Google Shopping, and Google Wallet) to support their online businesses and bring users into their offline stores. We are constantly innovating to deliver the most effective advertising and commerce opportunities of tomorrow. This is “hands-on” work with other systems and security engineers, to proactively identify and fix bugs, flaws and vulnerabilities in our software products. You will be placed in a specialist team where you will focus on the creation of software product development plans, software design reviews, and software development testing design across various Google products. In this role, you will often be analysing software designs and implementations from a user experience (UX) perspective and working to cultivate software development best practices across the company. You will develop solutions to help mitigate software vulnerabilities and promote excellent design and usability for users across Google products. You will work closely with other software engineers, programmers, product managers, legal and policy teams to build new features. The team are advocates of Agile software development but are also versatile enough to work with more traditional development approaches across the organisation and with other partners.
question 1
Google Digital Garage offers many short courses and certifications in several study areas and disciplines. When a user has been enrolled in one or more Google Digital Garage courses, their information is included in a relevant user database. During the session of a course, the user can access their Google Digital Garage dashboard with their user account. Generate at least one user story and two brief user acceptance test strategies based on the information provided. If you were asked to conduct a Detailed Blackbox Test for Google Digital Garage, would you need to inspect the software source code or user-interface for this platform? Explain why or why not.
User Acceptance Test
Step1: Analysis of business requirements
-Inlist all the short courses and certification in several areas
-When student will enroll themselves store their information in its relevant database.
-when user will login into his account so that he can access the dashboard with trir account information
in test cases we have to analyse these requirements.
Step2: Identify Test scenario and test cases
-test if all the short courses are listed
-test if enrolled student's data is getting stord in its relevant database
-test if user can access dashboard with their account details.
In this test we have to identify the testing scenarios
Step3:Run and Record the result
-if all the courses provided are displayed on the list
-test if enrolled user can access their services.
iIn this step we have to see for what input what output is provided by the system.
No, we can not inspect source code or user iterface in black box testing, because in black box testing we can only inspect input provided and output generated by system and what is the accuracy of ouutput for given input that only we can check in black box testing.