-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathnotes.txt
47 lines (32 loc) · 1.84 KB
/
notes.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
nouns1 = Person, Bike, Docking Station
nouns2 = Person, bike, bike
verbs1 = use, release
verbs2 = use, see, working
Objects messages Messages
<<<<<<< HEAD
Person interact with bike use a bike
Docking Station instance of bike release bike
Person condition(bike working or not?) use a good bike
Bike condition(working or not?) check working
=======
Person interact with bike use a bike
Docking Station instance of bike release bike
Person condition(bike working or not?) use a good bike
Bike condition(working or not?) check working
############## Stack Trace ################
A stack trace is a list of the method calls that an application
was in the middle of when an exception was thrown.
"A stack trace is a report that provides information about program subroutines.
It is commonly used for certain kinds of debugging, where a stack trace can help
software engineers figure out where a problem lies or how various subroutines
work together during execution."
https://www.techopedia.com/definition/22307/stack-trace
############## feature test ###############
A software feature is something that adds functionality or modifies functionality.
A feature test is a test set that tests the features according to what is required
for that softwares release.
Effective feature tests require an intimate understanding or specification of the feature.
Features tests should exclusively test that particular feature of the program.
Feature tests should cover positive, negative and boundary/edge cases.
Feature tests should be conducted from the beginning.
>>>>>>> da82c38cb9fbc18056c6e64926e24615300c165c