<p>We so can't wait to see you all at Granite State Code Camp 2022!<br><br>GSCC2022 is a one-day conference on Saturday, November 12th, 2022, simultaneously online AND in-person at Manchester Community College in Manchester, NH. The event is for the tech community that focuses on software development and software engineering. There is no charge for attendees. Dozens of professionals volunteer their time to share knowledge with fellow developers. All technology tribes are welcome, and topics are only constrained by what speakers volunteer to present (about code). There are a wide range of coding related topics that make Code Camp a popular and valuable event for professionals at all stages of their careers, rivaling conferences that cost thousands of dollars to attend. The conference is organized by software developers of the New Hampshire developer community who also volunteer, with the encouragement of the New Hampshire Technical Alliance and fiscal organizational support of Granite State Users Groups, LLC. Food, raffles and other considerations included in free admission are paid for in-person attendees by the generosity of our sponsors, who represent the best of the best community-promoting companies to work with and/or for in the Greater New Hampshire Area. #gscc2022 <a href="https://granitestatecodecamp.org">https://granitestatecodecamp.o...</a></p>

Granite State Code Camp

Story:
--------------------
After I was assigned to my new project, I realized that the quality assurance processes were not mature and we could introduce several initiatives to improve the quality (not only in the product, but also in our development activities). I will share my story which ended up in a successfully built quality.

With correct steps, we can see how quickly a quality process can be developed. But what is a quality process and how can we ensure quality? Does quality assurance equal to running tests? As you can guess, the answer is no. So we will talk about different aspects of quality assurance. By means of the initiatives I have introduced, we experienced not only the quality of the product, but also the efficiency of the agile ceremonies and visibility of information. We built a close working approach with Dev and Product teams to encourage early QA involvement and find ways to cope with testability issues.

Outcome
--------------------
While initially, there was:

* No track of bugs
* No feedback cycle on tests
* No transparency of the progress
* No organized feature
* No metrics, no idea about coverage
* Escaped bugs
* Massive manual effort 

After talking to product owners, development members and project leaders; I have initiated a number of studies. It was not a piece of cake since you have to act like a quality coach, be dedicated and encourage people. A few of the initiatives were Feature Housekeeping, Short and very understandable progress reports, Pulling QA in Early Stages and Bugs Management initiative.

A summary of the achievements are as follows:

* Features are organized and prioritized based on Criticality (Impact) and Probability (Visibility).
* Test cases are defined and documented. A Traceability matrix is generated from tests to features.
* Cases which are not testable are revealed, a testability improvement initiative is started.
* A test automation framework is built supporting re-usable automated tests.
* Locators are commonized across all sites by collaborative work with dev teams.
* Defined test cases are implemented to be executed on the CI pipelines.
* Test suites are generated based on priorities and Nightly jobs are scheduled.
* All results are reported and tracked publicly on Dashboards and Flaky tests are fixed.
* Test framework is used by several teams.
* Progressive metrics are tracked, traceability matrix is created, coverage is measured.
* Early QA involvement is encouraged by watching development tickets from T0.


Takeaways
---------------
Attendees will be able to see solutions to most common testing pitfalls:

* Managing product features and how to measure coverage
* How to cope with test-ability issues
* How to reduce duplication and improve reusability in test automation
* Dealing with test flakiness
* How to decide test suites and priorities
* Collecting insights from bugs
* Tracking various metrics to maintain a continuous improvement
* Early QA Involvement



The Tester’s Guide to Quality

X (Twitter)

LinkedIn

Blog

Company Website

Sessionize

The Metaverse is one of the big buzzwords that has been adopted by large tech companies in 2021 to the extent that Facebook's parent company even changed their name to Meta.

A core component of the Metaverse is ability to precisely locate oneself, real objects and virtual objects in a real environment and to be able to understand that environment.

This session looks at relevant Azure, software, and hardware technologies that help with this task such as Azure Spatial Anchors to enable the Metaverse.

Microsoft HoloLens 2 will serve as a demonstration device for those technologies.

After this session attendees will have a better understanding of what can enable a Metaverse that integrates with the real world.



Foundations of the Metaverse: Azure Spatial Anchors and Understanding 3D Space

Facebook

After graduating from a 6-month coding boot camp and switching careers, Jennifer Kirwin has been working at The ATOM Group for 2 years as a Software & Security Engineer. By attending her talk, you will learn what to expect from your first coding job out of school, day to day agency life, and what pursuing a career in software development is like followed by a Q&A session.

Your First Coding Job - What To Expect

Many organizations are using Databricks as part of their modern data warehouse estate.  This will introduce you to Databricks and resources for more learning.

Overview of Databricks for Developers

Github

Writing continuous integration YML scripts is a cumbersome and awkward process. What if there was a better way? GitHub Actions let you write JavaScript code to build, test, and deploy your applications. Even better, you don't have to write actions yourself but reuse the actions written by others. Plus the integration with the GitHub repo security lets your CI code easily contribute back to the repository or trigger other steps.