Section 1

Preview this deck

purpose of properties

Front

Star 0%
Star 0%
Star 0%
Star 0%
Star 0%

0.0

0 reviews

5
0
4
0
3
0
2
0
1
0

Active users

0

All-time users

0

Favorites

0

Last updated

6 years ago

Date created

Mar 1, 2020

Cards (56)

Section 1

(50 cards)

purpose of properties

Front

to modify or report the state of an object

Back

Everything is inherited except

Front

constructors

Back

UML for static

Front

<<static class>> underline static member

Back

base keyword

Front

represents an instance of the base class

Back

Unit

Front

smallexsft testable piece of code (one method/event)

Back

Base class constructors must

Front

always be invoked in the derrived class

Back

instances of a class have the same

Front

behaviours and attributes

Back

static classes can't...

Front

be instantiated/contain constructiors

Back

UML for properties

Front

<<property>> <<read/write only>>

Back

invoking properties is done

Front

contextually

Back

Class

Front

encapsulation of data and logic into one cohesive unit

Back

member of a static class

Front

msut be static

Back

unhandled exceptions

Front

abend the program

Back

UML for abstract

Front

italics

Back

Base Class

Front

the class being extended

Back

Static class are

Front

utility classes

Back

String Pool

Front

a table that contains a single reference to each unique literal string declared

Back

Exceptions

Front

an error or unexpected error when executing a statment

Back

Exceptions are

Front

objects

Back

stack trace

Front

exception property contains info re: where, what method, what value

Back

naming convention

Front

public Uppercase, private lowercase

Back

Anatomy of a class

Front

attributes, behaviours, constructors

Back

All objects derrive from

Front

System.Object

Back

units of code are tested in

Front

isolation

Back

tier

Front

one part of an application

Back

auto implemented properties are used when

Front

implemenetation contains no logic

Back

A class with an abstract method

Front

must be abstract

Back

overloaded constructor must be

Front

the first statment

Back

ToString for currency

Front

{:c}

Back

Method overriding

Front

a derrived class can provide it's own implementation for an inherited method

Back

3 tier architecture

Front

business, presentation, data

Back

steps for execptions

Front

1) construct instance of exception 2) throw exception 3) catch exception

Back

Methods and properties of abstract classes

Front

have no implementation, the MUST be implemented in the derrived class

Back

Abstract class

Front

a base class that is so generic it cannot be instantiated.

Back

Derrived class

Front

the class extending another class

Back

Source code compiles to

Front

CIL Common intermediary language

Back

steps in coding a class

Front

1. Using 2. Namespace 3. Class 4. Fields 5. Base Constructor 6. Overloaded Constructor 7. Properties 8. To String

Back

.NET is what kind of framework

Front

extensible (we can extend the abilities of classes

Back

2 parts of an assembly

Front

.exe executable, .dll dynamically linked library

Back

flow control

Front

try {} catch{}

Back

CIL compiles to

Front

*CLR Common Language Runtime

Back

UML representation of derrives

Front

open arrow head

Back

Enumerations are

Front

a 0-indexed collection of integer constants

Back

classes can derive from

Front

only one class

Back

Polymorphism

Front

a base variable may reference a derrived type A polymorphic operation has many implementations

Back

file types

Front

.sln solution, .cs c# source code, .suo solution user options, .csproj visual studio project, .resx resource file, config application configuration

Back

instances of a class have their own

Front

state

Back

what kind of methods can be overridden

Front

virtual

Back

Inheritance

Front

a class can be used to model other classes (blueprint)

Back

An abstract class may

Front

have non abstract members

Back

Section 2

(6 cards)

what to test

Front

every outcome of every behaviour, extremes and exceptions

Back

Private object

Front

allows test code to access methods and properties that are not public

Back

Unit test steps

Front

1. decare and define variables 2. Construct an instance of the class 3. Constuct an instance of private object 4.declare and define expected results 5. invoke the test 6. compare expected/actual results

Back

AAA pattern

Front

Arrange, Act, Assert

Back

Testing guidelines

Front

small, independant, test for one outcome, automate when possible, fix fail immediately, retest, naming standards, test everything

Back

visual studio team test

Front

test tools included in Visual Studio Test System

Back