You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Date

Attendees

Tyler ran a demo of the geb testing against the current tssg.tech web site.

Automated testing is an assignment for Mary, Thomas, Jess, and Tyler as homework for the next geb meeting. What worked this morning will have to be modified for the new, multipage v3.0.0 version.
Will also have manual testing to be able to cover what will need a visual test.

Jon gave a demo of the current multipage code.
Further changes to the current multipage code for Jon:
1. Footer and its icons are to be removed from mobile when in landscape mode.

Demo was done by Tyler of how to run and check results of geb automated tests.
What if google changes their address to the meeting place? Can we have auto tests handle that? Yes.

Ralph has 3 suggestions
1. Tests should be also put in source control. Need a test directory of the geb code with the source.
2. Before pushing to git, make sure files are using only linefeed for end of line (linux style). Avoid Windows use of cr/lf.
3. fix the source control file and folder permissions. directories should be 755 (executable and readable and listable); files should be 644 (read/write read read user, group, world); If not executable and should not be, like html, then it's not secure. The correct permissions for each file is important.

Edited the permissions on the directories and files associated with multipage. Had to use the git way to run chmod. Example below.
git update-index --chmod=-x Images/*.png     removing the executable bit

Merged multipage to master. Tagged as v3.0.0. It is now in tssg.tech as well as the MVP staging area. Singlepage was tagged with a 2.* version in case we want to view the previous version posted to tssg.tech.

Lora changed the current devops icon, similar to 1st version but with continuous arrows and no breaks 

OLD 

NEW


In preparation for opening a new project for gaining tech knowledge about current security and privacy issues... a new 'current event' for tech to discuss regards "commitments"; this news case should be on our radar.  Happened in the UK (GDPR issues?  in the US, may be a violation of HIPAA laws (The Health Insurance Portability and Accountability Act of 1996, HIPAA, establishes standards for the privacy and security of health information.))   Lora posted this link related to DeepMind's health app - acquired by Google in January 2014 under promises of privacy of data commitments - now in November 2018 being handed over to Google to manage the data. Article titled: "Google accused of 'trust demolition' over health app"   https://www.bbc.com/news/technology-46206677 


Ken requested that Jon move the schedule dates out of his scheduleDates.js file in order to keep data separate from code.  Jon agreed to do that with the next release. Eventually, we'll use a database for storage for schedule data.

Ralph set up a .gitattributes file to fix the crlf/EOL issue. Always saving with lf for unix/linux.
Ralph mentioned possible future IT setups with Ansible using playbooks.

  • No labels