Refresh your project vision with Report Portal
•Download as PPTX, PDF•
3 likes•1,355 views
This document summarizes how Report Portal integration improved one company's testing process. Key points include: - Collaboration and communication improved as stakeholders could easily see current project status through dashboards and widgets. - Test maintenance became easier and test behavior was clearer with Report Portal's features for investigating failures and tracking business logic expectations. - Senior leadership provided positive feedback, noting how Report Portal helped align the organization around quality by increasing testing frequency and allowing quick status summaries.
Report
Share
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Refresh your project vision with Report Portal
Similar to Refresh your project vision with Report Portal (20)
More from COMAQA.BY
More from COMAQA.BY (20)
Recently uploaded
Recently uploaded (20)
Refresh your project vision with Report Portal
- 1. Refresh your project vision with Report Portal
- 2. Konstantin Alesionok QA Analyst / QA Automation Lead DevOps Embrion Open source community member Skype: ikozzz Email: minskcitizen@gmail.com
- 3. @BeforePortal How Report Portal affected our process Go dirty Allure vs ReportPortal Feedback Few things to discuss
- 4. ● Sprint start ● Daily tasks ● Another urgent feature request ● Probably code freeze ● Regression testing ● Release @BeforePortal SomeProject
- 6. QA ’Em All Every single feature can be well tested not in real world. Highest priority first! We want awesome unit tests. Someone should look at test-reports.
- 7. How Report Portal Integration affected our process ● Collaboration improvement ● Easy automation maintenance ● More clarity on tests behavior ● Stakeholders can see current project state . ● … and some issues =)
- 8. What really has changed ??? “Investigation” feature helps to isolate automation-bugs from product We practicing new Business Logic Expectation technique now (some kind of broken BDD) People started to communicate more This matters for distributed developmenttestingmanagement teams (different time zones locations)
- 10. Highly customized solution micro-service micro-service many-micro-services
- 13. Microsoft - TFS Service https://github.com/reportportal/service-tfs [no docker yet] git clone https://github.com/reportportal/service-tfs.git [build container according to readme] ‘docker images’ (get your container name) add new service to ‘docker-compose.yml’ Start your environment
- 14. Add new block to ‘docker-compose.yml’ tfs: image: reportportal/service-tfs:2.6.1 depends_on: - registry environment: - reportportal.config.server.host=registry - SPRING_PROFILES_ACTIVE=docker restart: always
- 15. Good to go :)
- 16. docker stats CONTAINER CPU % MEM USAGE / LIMIT MEM % NET I/O 36f06a07eeca 0.11% 534.2 MiB / 7.6 GiB 6.86% 1.642 GB / 1.406 GB 51fvf16f428b 0.07% 367.7 MiB / 7.6 GiB 4.72% 390 MB / 74.1 MB e76fv3073bgb 0.37% 401.3 MiB / 7.6 GiB 5.16% 1.334 GB / 1.285 GB 444acd3d853e 0.08% 368.8 MiB / 7.6 GiB 4.74% 8.49 MB / 9.698 MB 17b8df80c3c3 0.08% 339.3 MiB / 7.6 GiB 4.36% 4.457 MB / 52.13 MB 1bc8v8df7h3b 0.69% 349.8 MiB / 7.6 GiB 4.49% 32.31 MB / 20.31 MB be33710eaf18 0.11% 6.328 MiB / 7.6 GiB 0.08% 784.5 kB / 642.6 kB 3jhg27g287gg 0.37% 2.015 GiB / 7.6 GiB 26.51% 1.367 GB / 766.6 MB
- 17. docker ps -a CONTAINER ID IMAGE COMMAND 36f06a07eeca reportportal/service-api:2.7.2 "java -Xmx256m -Djava" 51fvf16f428b reportportal/service-authorization:2.7.1 "java -Xmx256m -Djava" e76fv3073bgb reportportal/service-gateway:2.7.1 "java -Xmx256m -Djava" 444acd3d853e reportportal/service-tfs:2.6.1 "java -Xmx256m -Djava" 17b8df80c3c3 reportportal/service-ui:2.7.0 "java -Xmx256m -Djava" 1bc8v8df7h3b reportportal/service-registry:2.7.1 "java -Xmx192m -Djava" be33710eaf18 redis:3.2 "docker-entrypoint.sh" 3jhg27g287gg mongo:3.2 “entrypoint.sh --sma"
- 18. Replace it for readability docker stats $(docker ps --format={{.Names}}) CONTAINER CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS reportportal_gateway_1 0.18% 221.1 MiB / 1.943 GiB 11.11% 4.287 GB / 4.193 GB 1.111 GB / 9.155 MB 56 reportportal_ui_1 0.09% 152.9 MiB / 1.943 GiB 7.69% 10.26 MB / 74.41 MB 1.247 GB / 17.35 MB 40 reportportal_uat_1 0.07% 246.9 MiB / 1.943 GiB 12.41% 1.42 GB / 247.8 MB 1.131 GB / 8.729 MB 43 reportportal_tfs_1 0.09% 250.7 MiB / 1.943 GiB 12.60% 21.2 MB / 21.74 MB 1.404 GB / 138 MB 45 reportportal_api_1 0.08% 392.1 MiB / 1.943 GiB 19.71% 1.639 GB / 361 MB 2.318 GB / 287.6 MB 54 reportportal_redis_1 0.11% 1.383 MiB / 1.943 GiB 0.07% 6.901 MB / 5.625 MB 46.53 MB / 2.494 MB 3 reportportal_registry_1 0.61% 135.3 MiB / 1.943 GiB 6.80% 69.55 MB / 43.73 MB 900.6 MB / 270.3 kB 76
- 19. Moving mongodb data from 111.2.3.4 to 111.2.3.5 Server where mongodb is installed: (111.2.3.5) edit docker.compose file to resolve connection to mongo container from outside # mongodump --host 111.2.3.4 --port 37017 --out /opt/backup/mongodump-2017-04-20 111.2.3.4 111.2.3.5 MongoDB Docker RP container 1 Docker RP container N Docker MongoDB 123.1.2.3 port 27017 port 37017
- 20. Moving mongodb data from 111.2.3.4 to 111.2.3.5 Server where mongodb is installed: # mongorestore -h 111.2.3.5 -p 27017 -d reportportal /opt/backup/mongodump-2017-04-20 Restored MongoDB 111.2.3.5
- 21. Reconfigure ‘docker-compose.yml’ Shut down your RP if running Set new mongo host Remove ‘mongo_container’ and dependencies Check result Cleanup
- 22. Migration summary Isolated database Separate environment RP virtual machine 2GB RAM MONGO virtual machine 6GB RAM
- 23. Allure vs Report Portal ● What we do like in Allure ? ● What does Report Portal brings to us ? ● What profit we can get ? ● What else do we need from automation ?
- 24. Round one, Fight! Quick. Efficient. Usefull. No additional server needed Unique data representation Allure 1
- 25. Round two, Fight! Report Portal ● Powerful server application ● Easy tests aggregation ● Dynamic range of failure types ● Dashboards and Widgets ● Smart analysis
- 26. There is nothing to compare Allure 1 and RP is different tools and you may choose your own. Select best one regarding your requirements
- 27. Conclusion My clients reported me positive feedback about RP They liked how dev/management processes started to change Dashboards and widgets is a great visualisation tool for managers, who doesn’t care about ‘AssertionError’ :) But you should be careful. Client always want more. I already have few feature requests regarding RP
- 28. Real feedback President Quality and in particular QA Automation is essential to our organization. MyCompany is focused on customer engagement applications for subscription based companies. Our users are visitors to high traffic publishing sites. To ensure success for our clients and for MyCompany, we must deliver applications that have a rich and rewarding user experience. As we grow the number of clients and expand the scope of our application suite, we can’t lose focus on quality and the user experience. QA Automation and the work that Automation team performs allows us to scale without losing quality. In fact, we can improve quality. Automation leads to an increased frequency of testing. Automation and the dashboards of results helps us get the entire organization aligned around quality. Business Analyst As a business analyst for MyCompany, we face many challenges when presenting the status of test results for all of products and clients. Over the last year or so, the EPAM Report Portal has been a godsend in assisting in this endeavor. Project managers and lead developers now have one centralized app that quickly analyzes and summarizes the status of a product or feature, allowing for quick decisions on deployment cycle timelines and deployment schedules. Report Portal also helps us quickly report bugs, and determine root cause. Please keep up the good work on this project. I look forward to seeing this product evolve and mature.
- 29. Thank you