#build # NEAR BOS WebComponent Build Report ## Project Highlight: *What is the most exciting progress or achievement for the project so far?* NEAR BOS WebComponent makes it possible to view and interact with BOS content on any website. Create your own BOS gateway, or embed BOS component into any Web application or portal. The latest enhancements adds more configuration options to handle SEO friendly URLs, using the RPC of your choice, increase documentation and test coverage to ensure stability and backward compatibility for future additions. ## Team Effort: *What goals have/will demand significant contribution, and what did/will they accomplish?* The current NearSocialVM does not have an automated test suite, which means that fixing it or adding new functionality requires careful and thorough manual testing in order to avoid breaking existing functionality. It is currently hard to contribute to it, because it depends on thorough review by a few who knows the codebase to the tiny details. An automated test suite, would reduce the time needed for having to manually assess impact of contributions. Near BOS webcomponent is set up with the Playwright test framework, and is already equipped with several tests that also indirectly tests VM functionality. Extending the test suite to also include more variants of BOS components would also help to automatically assess impact on code contributions to the VM itself. A specific feature that needs further development is “Don’t ask again”, which improves user experience by not having to confirm with the wallet or transaction confirmation dialog for every submission or saving of some data. Implementing the test scenarios for “Don’t as again” in NEAR BOS webcomponent would improve velocity and reduce the risk of introducing bugs when developing this feature further. A specific feature that needs to be added to the VM now is https://github.com/NearSocial/VM/issues/105 which is about getting results from the transaction of a contract call. It is needed to provide proper feedback to the user about if the submission or saving of data was successful or not. In order to ensure a high quality implementation, that is also not delayed because of waiting for VM code owners, extensive automated testing coverage is crucial. ## Milestone: *Have you reached any key milestones? If so, what are they?* We have already reached the primary purpose of being able to provide a gateway for automated testing (which is used by NEAR DevHub), embedding BOS components into any web application or gateway ( which can be seen for the Social Media friendly links that also DevHub has ( e.g. https://devhub.near.page/community/webassemblymusic ). ## Upcoming Goals: **What is the next major goal or task for the project?** The next major goal is as mentioned in 2, to provide automated test coverage for the VM itself in order to boost development velocity by having automatic impact assessment of developer contributions. ## Visuals: **Any images, screenshots, or videos to share that showcase the project? 🙏🏻** https://www.youtube.com/watch?v=urO50ZYvt-8&list=PLv5wm4YuO4IwIqvkxSBV8LtW8UIpJVkcD