QA (Quality Assurance)

Quality assurance—often referred to as QA—begins after both content entryContent entry is the process of entering content into your w... and developmentDuring the development phase, your site (or new feature) is ... are complete and happens alongside proofreadingProofreading is the exacting but superficial scrutiny of a d.... This stage of the project ensures that what we’ve built for you works in all supported browsers as intended. During this process, a web producer or other team member who was not responsible for development on the project reviews the website thoroughly, testingQuality assurance—often referred to as QA—begins after b... custom functionalityFunctionality is a very general term we use to describe any ... in all supported browsers and on a variety of devices and screen sizes to ensure there are no critical bugs for the development teamThe development team builds and maintains the back end, incl... to resolve before launchLaunch is the process of making your website or web pages av....

Supported Browsers

Generally, your Statement of Work will specify which web browsers the project will support. If it does not, the project team will test in the latest version of all modern web browsers. Browsers that are no longer supported by their manufacturers are also not included in the QAQuality assurance—often referred to as QA—begins after b... process unless visits from these browsers comprise more than 10% of the browser usage for the website in the past year, as determined by Google Analytics. If the site is new, general analytics for bu.edu will be used to help determine if the browser should be tested.