Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
C
cas741-boliang
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Bo Liang
cas741-boliang
Commits
b21faf84
Commit
b21faf84
authored
2 years ago
by
W. Spencer Smith
Browse files
Options
Downloads
Patches
Plain Diff
Final lecture slides
parent
439347f4
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
Lectures/Deadlines.tex
+13
-13
13 additions, 13 deletions
Lectures/Deadlines.tex
Lectures/L25_Discussion/Discussion.pdf
+0
-0
0 additions, 0 deletions
Lectures/L25_Discussion/Discussion.pdf
Lectures/L25_Discussion/Discussion.tex
+21
-170
21 additions, 170 deletions
Lectures/L25_Discussion/Discussion.tex
with
34 additions
and
183 deletions
Lectures/Deadlines.tex
+
13
−
13
View file @
b21faf84
...
...
@@ -37,8 +37,8 @@ traditional SRS
%\textbf{POC Demo} & Week 06, 07 & Week of Feb 13, 27\\
% \textbf{MG + MIS Syntax} & Week 09 & Week of Mar 13\\
% \textbf{MIS Semantics} & Week 09 & Week of Mar 13\\
Drasil
&
Week 11
&
Week of Mar 27
\\
Unit VnV/Implement
&
Week 12
&
Week of Apr 3
\\
%
Drasil & Week 11 & Week of Mar 27\\
%
Unit VnV/Implement & Week 12 & Week of Apr 3\\
\end
{
tabular
}
\bi
...
...
@@ -56,7 +56,7 @@ Unit VnV/Implement & Week 12 & Week of Apr 3\\
\begin{frame}
\frametitle
{
Presentation Schedule
}
\bi
%
\bi
%\item SRS Present (25 min)
%\bi
%\item \textbf{Jan 26: Jason, Sam, Mina}
...
...
@@ -80,11 +80,11 @@ Unit VnV/Implement & Week 12 & Week of Apr 3\\
% \bi
% \item \textbf{Mar 16: Jason, Lesley, Deesha, Mina}
% \ei
\item
Drasil Project Present (25 min each)
\bi
\item
\textbf
{
Mar 30: Karen, Sam, Jason
}
\ei
\ei
%
\item Drasil Project Present (25 min each)
%
\bi
%
\item \textbf{Mar 30: Karen, Sam, Jason}
%
\ei
%
\ei
\end{frame}
...
...
@@ -94,11 +94,11 @@ Unit VnV/Implement & Week 12 & Week of Apr 3\\
\frametitle
{
Presentation Schedule
}
\bi
\item
Test or Impl.
\
Present (25 min each)
\bi
\item
Apr 5: Lesley, Deesha, Volunteer?
\item
Apr 6: Mina, Joachim, Maryam
\ei
%
\item Test or Impl.\ Present (25 min each)
%
\bi
%
\item Apr 5: Lesley, Deesha, Volunteer?
%
\item Apr 6: Mina, Joachim, Maryam
%
\ei
\item
4 presentations each (please check)
\item
If you will miss a presentation, please trade with someone else
\item
Implementation presentation could be used to run a code
...
...
This diff is collapsed.
Click to expand it.
Lectures/L25_Discussion/Discussion.pdf
+
0
−
0
View file @
b21faf84
No preview for this file type
This diff is collapsed.
Click to expand it.
Lectures/L25_Discussion/Discussion.tex
+
21
−
170
View file @
b21faf84
...
...
@@ -42,10 +42,7 @@
\frametitle
{
Discussions
}
\bi
\item
Start recording
\item
Administrative details
\item
Coding style
\item
Test report
\item
Questions?
\item
Discussion
\ei
...
...
@@ -58,183 +55,34 @@
\frametitle
{
Administrative Details
}
\bi
\item
Course evaluation
\bi
\item
Nov 23 to Dec 7
\item
\url
{
https://evals.mcmaster.ca
}
\ei
\item
GitHub issues for colleagues
\bi
\item
Assigned 1 colleague (see
\texttt
{
Repos.xlsx
}
in repo)
\item
Provide at least 5 issues on their MIS
\item
Grading as before
\item
Due by Tuesday, Dec 5, 11:59 pm
\ei
\item
GitHub issues for implementation
\bi
\item
Not required as part of course
\item
Will assign names anyway
\ei
\item
Source in src folder
\item
Added an INSTALL.txt file to BlankProjectTemplate
\ei
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle
{
Administrative Details: Deadlines
}
~
\newline
\begin{tabular}
{
l l
}
\textbf
{
Final Documentation
}
&
Dec 18, 11:59 pm
\\
\end
{
tabular
}
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle
{
Coding Style
}
\bi
\item
Having a coding standard is more important than which standard you use
\item
Examples
\bi
\item
Google guides
\bi
\item
\href
{
https://google.github.io/styleguide/pyguide.html
}{
Python
}
\item
\href
{
https://google.github.io/styleguide/cppguide.html
}{
C++
}
\item
\href
{
https://google.github.io/styleguide/javaguide.html
}{
Java
}
\ei
\item
\href
{
https://developer.mozilla.org/en-US/docs/Mozilla/Developer
_
guide/Coding
_
Style
}{
Mozilla
Developer Network
}
\item
\href
{
http://homepages.inf.ed.ac.uk/dts/pm/Papers/nasa-c-style.pdf
}{
NASA C
Style Guide
}
\ei
\item
Your decisions on style may evolve over the project
\item
Important to be consistent
\ei
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle
{
Installability and Learnability
}
\bi
\item
You can test this
\item
Ask a colleague to install your software
\item
Run it on a virtual machine, like
\href
{
https://www.virtualbox.org/
}{
VirtualBox
}
\item
Use a ``light weight'' VM like docker
\item
Include installation instructions (INSTALL.txt)
\item
Include instructions so that someone else can run your tests cases
\ei
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle
{
Final Documentation: Test Report
}
\item
\href
{
https://mcmaster.bluera.com/mcmaster/
}
{
Course evaluation
}
\item
Reverse engineer MIS from your code
\item
Check the type for all variables
\begin{itemize}
\item
Completing what you proposed in your test plan
\item
You do not need to repeat material from your test plan - the emphasis is
not on the rational for test case selection, but on the results.
\item
If your test plan does not match what you are now testing, edit your test
plan to ``fake'' a rational design process.
\item
$
\mathbb
{
R
}$
versus
$
\mathbb
{
R
}^
n
$
\item
$
\mathbb
{
R
}
\rightarrow
\mathbb
{
R
}$
\end{itemize}
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle
{
Test Report Continued
}
\begin{itemize}
\item
Provide specific test cases
\item
Summarize your test results
\bi
\item
Test case name
\item
Initial state
\item
Input
\item
Expected results
\item
Whether actual output matched expected
\item
Abstract object versus Abstract Data Type
\ei
\item
Summarize and explain usability tests - quantify the results
\item
Performance tests - quantify the results
\item
Stress tests
\item
Robustness tests
\item
After quantification of nonfunctional tests, explain significance of
results
\end{itemize}
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle
{
Test Report Continued
}
\begin{itemize}
\item
In cases where there are many similar tests
\bi
\item
Summarize the results
\item
If the expected result is obvious, you might not need to state it
\item
Give an example test case, and explain how similar tests were constructed
\item
If the tests were random, describe how they were selected, and how many,
but not all of the details
\item
Use graphs and tables
\item
You need enough information that
\bi
\item
Someone could reproduce your tests
\item
Your test results are convincing
\item
Evidence that you have used testing to improve the quality of your project
\ei
\ei
\end{itemize}
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle
{
Test Report Continued
}
\begin{itemize}
\item
Summarize changes made in response to test results
\item
Explain your automated testing set-up (if require more detail than from
the test plan)
\item
Provide traceability to requirements (if not in test plan)
\item
Provide traceability to modules (if not in test plan)
\item
Make sure you show test results for ``bad/abnormal'' input
\end{itemize}
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\input
{
../Deadlines.tex
}
\begin{frame}
\frametitle
{
Sample Test Report Documents
}
\bi
\item
\href
{
https://gitlab.cas.mcmaster.ca/screenholders/screenholders
}{
Screenholders
}
\item
\href
{
https://github.com/palmerst/CS-4ZP6/tree/master
}{
2D Physics Based Game
}
(Uses doxygen)
\item
\href
{
https://gitlab.cas.mcmaster.ca/smiths/cas741/tree/master/BlankProjectTemplate/Doc/TestReport
}{
Follow given template
}
\item
Examples are not perfect
\item
Examples are intended to give you ideas, not to be strictly followed
\item
You can modify/extend the test report template as appropriate
\ei
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle
{
Questions?
}
\begin{itemize}
\item
Questions Final documentation?
\item
Final documentation?
\item
SRS revisions?
\item
VnV Plan revisions?
\item
MG and MIS revisions?
\item
VnV Report?
\item
Code?
\item
Drasil projects?
\end{itemize}
\end{frame}
...
...
@@ -256,8 +104,8 @@
\item
Git
\item
GitHub
\item
LaTeX
\item
Make
\item
Your programming language
\item
Drasil projects
\ei
\ei
...
...
@@ -287,8 +135,11 @@
\bi
\item
What can be done to improve the course on its next iteration?
\item
Increase number of reviewers for GitHub issue creation?
\item
How to get more discussion in class?
%\item Increase number of reviewers for GitHub issue creation?
%\item How to get more discussion in class?
\item
Any need to address the heterogenous mix of knowledge between students?
\item
Did anyone use the checklists? Enforce with template issues?
\item
Anything to add to the checklists?
\ei
\end{frame}
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment