dipdb_ictprg529_powerpointslides_session2

11
APPLY TESTING TECHNIQUES FOR SOFTWARE DEVELOPMENT ICTPRG529

Upload: careers-australia

Post on 16-Aug-2015

36 views

Category:

Education


0 download

TRANSCRIPT

Page 1: DipDB_ICTPRG529_PowerPointSlides_Session2

APPLY TESTING TECHNIQUES FOR SOFTWARE DEVELOPMENTICTPRG529

Page 2: DipDB_ICTPRG529_PowerPointSlides_Session2

SESSION 2 OVERVIEW

• Development, Test and Production computing environments

• Test plans

• Assessment 2 overview

Page 3: DipDB_ICTPRG529_PowerPointSlides_Session2

• Software created must first be extensively tested before going ‘live’

• Testing should never be done on the production servers or

computers

• Test server may sometimes be referred to as ‘staging’ server

• Production servers can be replicated for fail over protection

Test environments

Page 4: DipDB_ICTPRG529_PowerPointSlides_Session2

• A test plan can have the following sections as a minimum:

o Project title

o Documentation for revision history

o Introduction describing the project

o What’s in and out of scope

o The hardware and software of the testing environment

o Details of each test to be done

o Sign-off and feedback for each test done

o Contact person regards the testing

o Archived material so the test can be replicated in full at a later

date

Test plans

Page 5: DipDB_ICTPRG529_PowerPointSlides_Session2

Global Holidays – sample test

Page 6: DipDB_ICTPRG529_PowerPointSlides_Session2

Global Holidays relational database mud map

Page 7: DipDB_ICTPRG529_PowerPointSlides_Session2

The Global holidays database data (1)

Cities

Hotels

Countries

HotelPhotos

Page 8: DipDB_ICTPRG529_PowerPointSlides_Session2

The Global holidays database data (2)Rooms

BedTypes

Page 9: DipDB_ICTPRG529_PowerPointSlides_Session2

The Global holidays database data (3)Guests

Bookings

Page 10: DipDB_ICTPRG529_PowerPointSlides_Session2

Global Holidays normalised tables

GlobalHolidays database:Countries (CountryID, Country)Cities (CityID, City, CountryID)Guests (GuestID, [FirstName], [LastName], [Gender{M,F}], [CountryID], JoinDate, [Email], [Password])Hotels (HotelID, HotelName, CityID, [ParkingSpaces], [PetFriendly], [JoinDate], [HotelViewDesc])HotelPhotos (HotelPhotoID, HotelID, HotelPhotoName, MainDisplayPhoto{Y,N})BedTypes (BedTypeID, BedTypeDesc)Rooms (HotelID, HotelRoomNum, BedTypeID, [RoomDesc], [StandardPrice], [Sleeps])Bookings (BookingID, GuestID, HotelID, HotelRoomNum, Checkin, Checkout, [NumGuests]) Notes:- Table names are in bold- Primary keys are underlined- Foreign keys are not explicitly labelled as foreign keys- Columns that can have NULLS i.e. it is optional to enter data in them, are in [square brackets]- Columns where the data entered can only be one of the listed alternatives are in {curly brackets separated by a comma} e.g. Gender {M,F} means a user can only enter a ‘M’, or a ‘F’ (M=Male, F=Female)

Page 11: DipDB_ICTPRG529_PowerPointSlides_Session2

ANY QUESTIONS