Blog Posts

Week 19 – Virtually Working

There was no class this week for IPPD so instead the Quarks met online to work on ATOM! All team members joined a call and separated into breakout rooms based on our two development teams, Framework and UI.

Integration between the two teams has already started and will be a continuous process. We recently integrated the current Framework with the current UI and we are able to call our testing scripts to run with working functions and UI to start, stop, pause, and resume tests. Approval was received to move forward with Powershell which will be our current main resource for automation. Our scripts can now also run on the Virtual Machines that reflect their end use case environment. As the report page UI work continues, we have started creating the test creation page. This will allows users of ATOM to create their own tests on the spot ideally without needing any previous coding experience. The current approach to this is to create scripts that have different functions like building blocks, and the user can select which blocks they want and in what order they should occur. This is what we refer to as modularization of the automated testing process. Our prototype test creation page from the fall shows our initial vision allowed for steps to be added and deleted with the preferable action and result for each step.

Test creation page from the fall semester prototype.

Week 18 – Progress and Setbacks

This week Marked the start of sprint 3 for the ATOM project. The sprint goals are currently to complete the report generation page for the UI side and ensure the running of scripts for the backend side.

The homepage for ATOM is nearly complete and the UI team has started working on the report generation page and account management page. A number of the frameworks and automation software we were looking into will not be able to continue within the development of ATOM. The Robot Framework is not viable and AutoHotKey is on delay while it awaits clearance from our sponsors. While this is a hiccup, we are currently looking into alternative automation tools for development including Powershell which is a promising option. Discussion on how to approach modularization is also starting as we start looking ahead into future goals.

Powershell logo.

To end the week, we had a meeting with our coach and the other RTX team Banary. It’s always encouraging to hear their progress as another computer science team. We weren’t able to meet with our liaisons this week but we will continue communicating throughout the week with any questions we have.

Week 17 – Quality Review Board 1

Accomplishment slide from QRB1.

This week the Quarks had their first meeting with the Quality Review Board (QRB1) where we presented the status of our project and our initial development goals and accomplishments. We met multiple times beforehand to practice presenting as a team to ensure we all knew our parts and that we flowed smoothly from one member to the next. On presentation day, our board consisted of our coach Dr. Resch, Dr. Latorre, Dr. Abd-Elrahman, and Dr. Patrick. The presentation highlighted our prototype from last semester, our current successes within our two teams, and the plan for this upcoming semester. We received valuable feedback on both the content of our slides and our presentation of it which we will definitely incorporate for QRB2.

As for accomplishments, both teams have been making steady progress. The UI team has successfully implemented tab logic, created run and stop test buttons, and an overview of the test results page! The framework team is almost finished automating the test processes provided by RTX and will begin modularization of the automation process shortly. We are also working on getting a more accurate measure of how long the testing process would take manually using the provided test cases.

This week was also the start of our liaison meetings again! The team was able to meet with Joseph Foraker and Alex Good along with our coach Dr. Resch. We were able to ask question we had about the project and get clarification on certain aspects we were unsure about. We also discussed setting up a meeting with the test engineers to get feedback on ATOM!

See you next Sprint!

Week 16 – Initial Development

January Work Plan

This week is showing amazing progress for the Quarks. Both the UI and Framework teams are getting good work done and we are moving along on schedule as January slowly comes to an end. It has been a change of pace starting development versus last semester but we are getting into the swing of things. As a team, we have begun creating the presentation for Qualification Review Board 1 (QRB1) and also divided up roles. We will continue to work on the presentation, finalize it, and practice presenting it before next week.

Initial Home Page

The UI team is working on basic functionality of the home page including a start button to run an initial test. This test is currently run from a specified file path which is displayed below the start button. We are currently using our wireframe prototype from the fall semester as a guide for designing UI components. The Framework team is working on developing automated scripts for the remainder of the provided test cases. Once all of the test cases are automated, we are going to begin modularization of the test frameworks. Basically, we want to make a user-friendly system for easily adding new test cases using our framework and tools.

Week 15 – First Week Back!

RobotFramework homepage

Welcome back to IPPD! As we enter the spring semester and the Quarks transition out of winter break, there are a lot of exciting things happening and we are quickly getting back into the swing of things. The Fall semester went amazing and we have a plan for the proposed solution we will be creating. A quick recap, we are working with RTX to create ATOM, an automated testing suite to help streamline software testing. Our proposed solution is a desktop application that utilizes automation software to pre-program these processes and carry them out automatically. We have divided into two teams, UI and Framework.

We are currently in our first sprint with the main goal being creating a base test processes to ensure the functionality of our solution. The UI team is working with desktop application development to create a layout for the suite. Meanwhile the Framework team is utilizing software like RobotFramework and AutoHotKeys which allows testing scripts to simulate human-computer interaction and automate it. We are happy to be back and very excited to continue developing our project!

Week 14 – Wrapping up the semester with SLDR!

Quarks presenting the SLDR.

Presenting our System Level Design Report for ATOM is a major milestone for IPPD and marks the end of the fall semester! The SLDR is the culmination of our efforts and work this semester and we were so proud and excited to showcase it. After making many improvements and adjustments using feedback from our peer presentation, we practiced presentation flow, timing, and cohesion to ensure the presentation was as smooth as possible. Before the presentation, the Quarks had a chance to speak with other IPPD teams and learn about the professional world from other liaisons. It was a great opportunity to speak with veteran engineers from different fields who have so much experience and insight to offer. Showing off our SLDR and presenting all of the hard work we put in this semester was incredibly rewarding for the Quarks. We also had the privilege to watch Banary and Gear Guardians present their SLDR. As a fellow RTX sponsored team, we shared many events and milestones with Banary and watching their progress alongside ours was both insightful and encouraging.

It has been quite the rewarding journey for the Quarks. Going from strangers to teammates, creating our scope of work to presenting our PDR and now SLDR, and even the first prototype for ATOM. Although this semester is now over, we are not finished. The spring semester will see us enter the development phase of ATOM starting with initial test automation and functionality and eventually resulting in our final prototype solution.

We would like to give a special thanks to our liaisons Joseph Foraker and Alexander Good, our coach Cheryl Resch, executive sponsor Kathryn Frain, and all the IPPD staff who helped us along the way. This has been an amazing fall semester and we look forward to continue working in the spring!

Week 13 – First Presentation of our SLDR

A section of our Spring Project Plan from the SLDR

After a successful week presenting our prototype for ATOM (Automated Testing Operations Monitor), this week we presented to our peers the current System Level Design Review (SLDR) for project ATOM. We had a few unexpected occurrences (the laptop died mid-presentation) but the Quarks still had a successful presentation! Additionally, some slides were overly wordy causing us to go over the time limit. The feedback we received was very helpful and easily actionable and these changes can be immediately implemented to improve our presentation. Feedback includes visual changes, reducing wording, better time management, and various clarifications on some of the technical content we presented. The team will be working on these changes along with any other improvements over the next week in preparation for the final SLDR presentation December 3rd.

As the semester nears its end and the Quarks prepare for the final presentation of the SLDR, we are starting to make objectives for both the user interface and framework teams looking ahead. Thanksgiving break will be used to improve our presentation and finalize the SLDR itself. After that, we are looking to complete and implement an initial test case, the UI team will begin work on the homepage, and the framework team will being automating the first set of testing processes.

Happy Thanksgiving from the Quarks!

Week 12 – PID!

The Quarks presenting the ATOM wireframes

This week we had Prototype Inspection Day! The Quarks were busy working on the prototype that was showcased to pairs of judges. Together the team presented wireframes that would represent the user interface of our proposed solution to the ATOM project. We had a great time showing off our progress together as a team and were grateful of all the feedback we received. A number of action items have been created based on this feedback to improve upon the solution. We split these items up among the team and have already started tackling them. The prototype wireframes are going to be sent to the testing engineers at RTX for additional feedback.

The SLDR is underway and the sections have been assigned throughout the team. The presentation for the SLDR is also being made including information from our PID and the new sections. We will have a good draft for the peer review presentation this upcoming week. Using the peer review feedback, we will finalize the SLDR for December 3rd.

While the UI team has put in a lot of work for the prototype wireframes, the framework team had its first team meeting today in the Hatchery to brainstorm implementation of the automated tests. Currently, we are researching existing automation tools.

Week 11 – The Hatchery

This week we set up the Hatchery and turned on the machines with the help of our primary liaison, Joseph Foraker. The work stations will provide a secure area for us to develop the testing suite and we expect to start holding meetings here for the test framework team.

Work on the wireframes for our prototype is nearly complete. The wireframes will inspire the final user interface of the test suite and will showcase all the functionality we hope to include in our solution. The UI is sleek and offers a dark color palate to be easier on the eyes. Although we are excited to share our progress, we can only reveal what we have done during our PID next week. The framework and UI teams are in the process of scheduling sub meetings to start brainstorming and shorty after that, development. The testing processes we received are being analyzed and we have a better idea of how to start automating them. From this, we also gained some insight on how to approach allowing the user to add their own tests in the future.

Also this week, the Quarks met with their coach to discuss midterm evaluations. We received good feedback on how to improve moving forward and what we might need to work on. Overall the whole team is doing great and we are progressing quickly. We’ll see you after PID!

Week 10 – Picking up the Pace

Matching RTX polos

Things are moving quickly for the Quarks this week. Since we’ve gained access, we have been exploring our new workspace The Hatchery, and getting used to the new area. Our final PDR is completed and has been signed off by the team and our liaisons. The feedback we received was extremely helpful and has guided us when considering how to approach our project prototype, specifically how technical or non-technical the solution will be. Prototype Inspection Day is a little over a week from now and we have made lots of progress on the wireframes that will representing our solution. The wireframes showcase the various pages of the application including the home page, test selection page, and test report page. The Quarks have also split into two teams, one for the front end UI design of the application and the other will handle the back end framework.

Last but not least, we have received testing procedure resources from RTX and we will begin analysis on it right away! This will be a great look into how testing is carried out and how we can best implement our automated solution. We also got matching polos provided by RTX!