{"id":2388,"date":"2022-06-03T08:02:06","date_gmt":"2022-06-03T08:02:06","guid":{"rendered":"https:\/\/blog.embold.io\/?p=2388"},"modified":"2022-06-06T10:22:46","modified_gmt":"2022-06-06T10:22:46","slug":"repository-scan-performance-testing","status":"publish","type":"post","link":"https:\/\/blog.embold.io\/de\/repository-scan-performance-testing\/","title":{"rendered":"Repository Scan Performance Testing"},"content":{"rendered":"\n

Before we get into the exact testing approaches\nthat we use, we’d want to talk about the different levels of granular\ntesting.<\/strong>   <\/p>\n\n\n\n

Let’s look at a software system, which is made up of interconnected components. The first level of testing that we consider in testing is Unit Testing<\/strong>, which involves testing individual components in isolation. <\/p>\n\n\n\n

Integration Testing<\/strong> is the next step, which involves examining\nnumerous components and their interactions. Know more about\nhow Embold can be used by QA teams.<\/a> <\/p>\n\n\n\n

And after the integration testing, the next\nstep is to test the complete system as a whole.<\/strong> It includes both functional<\/strong>\nand non-functional testing. <\/strong> <\/p>\n\n\n\n

Performance\ntesting<\/strong> is an important aspect of testing\nsince it aids in the improvement of performance. It’s a type of non-functional\nsoftware testing that ensures software programs will run smoothly under the\npredicted load. The goal of performance testing is not only to find bugs but also\nto eliminate performance bottlenecks. Performance testing examines the speed<\/strong>,\nscalability<\/strong>, and stability<\/strong> of a software program. Every new\nversion is subjected to performance testing by Embold.<\/strong><\/p>\n\n\n\n

Acceptance testing<\/strong> and regression testing<\/strong> are two more\ntypes of testing. <\/p>\n\n\n\n

Acceptance testing<\/strong> is the validation of software against the customer requirements. So, this is the testing that makes sure that the system does what the customer wants it to do. <\/p>\n\n\n\n

And the last type of testing is Regression\ntesting. <\/strong>It is a type of testing or retesting that we perform every time\nthat we change our system and make sure that the changes behave as intended and\nthe unchanged code is not negatively affected by the modification by these\nchanges.  <\/p>\n\n\n\n

So,\nfor many projects, the test processes that run,\noccupy a significant amount of time during the construction phase. These tests\ncould be a mix of unit and integration tests, with the latter taking the most\ntime.<\/strong> <\/p>\n\n\n\n

How we, at Embold, do granular\nperformance testing by analysing the performance of every component?<\/strong> <\/h2>\n\n\n\n

Before\nevery release, Embold carries out an automated performance testing for all\nmajor languages. With each new version, we have more rules introduced that influence\nthe scan performance. But our goal is to ensure that the difference in performance\nis as small as possible.  <\/p>\n\n\n\n

Test\ndata consists of large, medium, and small-size open-source repositories. We\nbenchmark the performance to the scan time for the last release for\nrepositories with similar lines of code. <\/p>\n\n\n\n

In case there is an improvement in scan\nperformance, we consider that as our new benchmark. <\/p>\n\n\n\n

But\nif the scan performance has deteriorated, we do a more granular performance\ntesting. Embold scan process consists of multiple small components which\nperform the following tasks <\/p>\n\n\n\n