Week 1 Plan and Review

Credits to @hope_house_press_leather_diary_studio


These were the Goals we set to do on Week 1:
  • Get familiar and a brief introduction to software testing.
  • Read Chapter 1 of the Introduction to Software Testing Book.
  • Define team roles.
  • Figure out which project are we going to be working on this semester.
  • Share Github credentials (Usernames).
  • Set up Github Team Repository.
  • Brief Review on how to use Github.
  • Get to now each other, by sharing cellphone numbers and creating a WhatsApp group.
What we actually accomplished:
  • We did get acquainted with Software Testing by reading Chapter 1 and solving some doubts with one and other.
  • As for assigning team roles we decided that Frida is going to be our team captain (maybe).
  • We couldn't settle on which project we're going to be working on because we haven't define those projects in our other classes, they're still pretty abstract at the moment.
  • We finished our Class Activity #1 that consisted on setting up the Team´s Github Repository, so naturally we shared our Git usernames.
  • Frida created the team WhatsApp group so we can communicate a lot easier.
Weekly Planning Through the Semester:
  • Set software tests for the project the we choose.
  • Functional Testing
  • Validation
  • Verification
  • Minimize software risks
  • Implement new software testing techniques

Team #1
Frida 
Valentin
Floreth

Comments

Post a Comment

Popular posts from this blog

Chapters 6.1 & 6.2

Image
Credits to @4vid Image Link 1. What two properties must be satisfied for an input domain to be properly partitioned?  Completeness: The partition must cover all of the domain. Disjoint: blocks should not overlap 2. What is an Input Domain Model (IDM)? Two Approaches to Input Domain Modeling: A. Interface-based approach. 􏰀 Develop characteristics directly from individual input parameters. 􏰀 Just use properties of the domains without considering the actual function under test. B. Functionality-based approach 􏰀 Develop characteristics from a behavioral view of the program under test. 􏰀 Use your understanding of what the system should do. 3. What gives more tests, each choice coverage or pair-wise coverage? Each Choice Coverage (ECC) states that one value from each block for each characteristic must be used in at least one test case. For example, for partitions [A, B] [1, 2] we can get [A, A], [B, B], [1, 1] and [2, 2] which are clearly redundant. Pair-
Read more

Final Exam Questions

1. Software fault: static error in the code. Software error: internal, not a normal behavior of the program due to a fault. Software failure: external, visible failure of the program. That it doesn't work basically. 2. Beizer discussed the goals of testing in terms of the “test process maturity levels” of an organization, where the levels are characterized by the testers’ goals. Level 0: Testing and debugging are the same. (Worst level) Level 1: Testing is only to find that your code doesn't work. Level 2: Get defensive or make an issue personal with testers because they broke your code. Level 3: Understand the job of a tester and take feedback as constructive criticism. Level 4: Become an expert software tester and make extreme good quality software. Work in harmony with testers. 3. Static Code Analysis is usually performed as part of a Code Review (also known as white-box testing). is a method of debugging by examining source code before a program is run . It’s done by ana
Read more

Course evaluation

Image
Credits to @rossf Image Link ECOA Evidence  I've been Ken Bauer's student for almost four years in several different courses, and his teaching method has always been a breath of fresh air. From flip learning to almost conventional teaching (since you grade your own exam) he's not afraid to make changes and give students the chance to explore self learning and to take responsibility on when and how they learn the content of the course. This is a skill that is very important acquire and that is needed on a daily basis in every job in the tech field. Personally i enjoyed the Software Quality and Testing course. There are many students that might not like this method of teaching applied on this course because it requires them to take responsibilities on their own learning and some students can't handle this type of control over their own learning. No negative feedback for this course, only that maybe some classes should be online.
Read more