Presentation Description

No description available.


Presentation Transcript

Experiment Instructions:

Experiment Instructions

A fewthings:

A few things Change in plans Purpose of the experiment Before the experiment During the experiment After the experiment

Schedule Lectures and Seminars:

Schedule Lectures and Seminars Outcome Learning and Teaching (Four instruments for learning: Problem sets, Assignments, Lectures, Seminar) (Wed Jan 19) w3 (08:00-12:00), always in room Gradängsal G340 Introduction to Verification and Validation and Course Content, Handout of Problem Set 1 (Fri Jan 21) w3 (08:00-12:00) Static Validation techniques, Handout of Problem Set 2 (Fri Jan 28) w4 (08:00-12:00) Software Reliability, Handout of Problem Set 3 (Fri Feb 4) w5 (08:00-12:00) Home Experiment (Deadline 10 th of Feb.) – no lecture on Friday (Fri Feb 11) w6 (08:00-12:00) Dynamic Validation – Test Design 1, Handout of Problem Set 4 (Fri Feb 18) w7 (08:00-12:00) Dynamic Validation – Test Design 2, Handout of Problem Set 5 (Fri Feb 25) w8 (08:00-12:00) Verification and Validation Processes (Test levels, Testing processes, Measuring testing efficiency) , Handout of Problem Set 6 (Fri Mar 4) w9 Seminar - Case Studies (Fri Mar 11) w10 Home Experiment (Deadline March 11) – no lecture on March 11


Assignments Assignment/Evaluation Content ECTS/Dates/Grade Assignment 1 Evaluate a piece of software with static validation techniques (static code analysis/inspection) 1,5 (groups of four) Grade: A-F Deadline: 18. Feb. 23:00 Assignment 2 Apply reliability prediction techniques on a set of fault data 1,5 (pair) Grade: A-F Deadline: 25. Feb . 23:00 Seminar Presentation and critical reflection on a research article in the area of software testing 1 (Individual) Grade: Pass/Fail Occasions: Mar 4 Written examination Preparation through problem sets, and written exam (closed book) 3 (individual) Grade: A-F Occasion: TBA Resubmission: Two weeks after corrections have been provided to you.

Purpose of the experiment:

Purpose of the experiment Purpose: Gain experience at different stages of the course in developing and testing software You should solve a problem to gain experience, this is not part of the evaluation, i.e. you will not receive a grade for the experiment! Don’t worry about your development skills, you will not have an advantage/disadvantage in the examination However, the experiment is mandatory and you should do your best, i.e. you have to commit your code changes We will collect data and treat the data anonymously to evaluate the course (not you!)

Before the experiment:

Before the experiment There are two rounds of the experiment Development exercise A available: Feb 3., deadline completion: Feb. 10 Development exercise B available: Feb 25 deadline completion: March 11. For each experiment you will receive an instruction mail, you will only receive a mail when you are registered in lärarportalen (hence make sure to check your mails) Familiarize yourself with the development environment that you should use. Subversion – SVN Usage of the Eclipse Environmen

Before the experiment (Software):

Before the experiment (Software) Get Java for Windows and install http://www.java.com/en/download/inc/windows_new_xpi.jsp Get Eclipse IDE for Java Developers and install http://www.eclipse.org/downloads/ Get Subversion (Tortoise) http://tortoisesvn.net/downloads.html If you have L inux, consult your package manager 

Before the experiment:

Before the experiment In case you have not worked with Eclipse before, you should familiarize yourself with the IDE and how to run test cases http:// eclipsetutorial.sourceforge.net/totalbeginnerlessons.html

Before and during: IMPORTANT:

Before and during: IMPORTANT For experimental reasons and not biasing the results: Do not share your instructions/ tasks with your peers, and do not talk about them Do not look up the solution on the internet (i.e. keep your firefox /chrome/etc. closed), otherwise the task does not make sense!

During the experiment:

During the experiment Instructions for the use of SVN in combination with Eclipse are provided here for download: https://sites.google.com/site/kaipetersen79/files/EclipseandSVNInstructions.pdf?attredirects=0&d=1 After you have checked out your code/instructions you have three hours for the task The checked out folder contains: The code skeleton for you to work with Lab Instructions (Read them carefully and follow them!) A text file “Number of user stories.txt ”. After three hours, do not commit anymore changes. Add the number of user stories to “Number of user stories.txt ”.

After the experiment:

After the experiment After having commited your code for the first probem , you will do the same on the second occasion After the course I will summarize/make an analysis of the data collected and provide you with a summary of what we can learn about software testing based on the experiment.

Thank you..:

Thank you.. for your participation  If you have questions, drop me an e-mail!

authorStream Live Help