DAMLA IYILIKSEVER | BUSINESS ANALYST
Which firm or person that is aiming to develop software and focuses on publishing a good product does not want it to be perfect? I seem to hear you saying: “Of course, it should be error-free! This is deadly important for my company’s prestige.”
Well… Have we ever thought that how can we be sure about is our product “perfect” or not?
People have the main idea and accept the job is all done if they are near to finish line. They miss a very important point here; Test Processes. Most of the companies do not attach importance to testing, do not write the test codes and they consider testing as a waste of time. This contrarian understanding with time management is adopted by many companies.
Let’s make you clear about what is software testing. Software testing is made for analyzing software supplies with the expected needs and features or not. Please note that it is a big mistake believing that these test phases are only for testing software. Screens’ usability (visuality, encolouring, type font and size, design, functional-none functional details) that end-users will experience can be tested from the point of end-users.
Even you have a problem with the situation of your product’s delay because of the test phase and processes, testing will decrease your costs in a long-term by including early bug determination and bug prevention actions. It provides you to gain trust and satisfy of your customers and thus, your product’s quality will be raised. The truth is that prestige will come along with these test requirements indisputably. There are various test management tools can make you satisfied with your product’s quality issue in the market. Let’s check on them:
TestRail: It is a test tool which is preferred by large informatics companies due to its ability to be accessed via web and to configure the fields it contains and to be integrated with error tracking tools. It can provide users procure many report types (created test cases, taken bugs, test comparisons, feature distribution, test plan summary, user workloads etc.). “Todos” section includes user’s and team members’ test conditions and it’s possible to filter case status and scenarios. There are various integrations with platforms like Lighthouse, Manuscript, Mantis, PivotalTracker, Rally, Redmine, TFS, Trac, Vault, VisualStudio, Online, You Track, Bitbucket, BugTracker.NET, Bugzilla, Fixx, GitHub, JIRA. I guess management screens’ convenience is one of the reasons of preference by firms. Together with its benefits and features, there are some reasons not to choose by several companies as you can guess because of the cost factor.
Case.io: Accessing it via web, usage simplicity and convenience, being a Cloud-based tool, adding “unlimited” team members, preparing result reports and sharing them through URLs, sharing all test conditions with all team members in “shared steps” section, adding milestone feature, filtration of case status and Import/Export option may make this tool attracted for the companies. Here is the bright side, you can reach these all features on free version. It has JIRA, Redmine, YouTrack, Slack integrations at the same time and the information on many other platforms’ integration will exist in near future has given. It has a paid version normally but of course, you can choose the version according to your needs. It is more acceptable that the other test management tools because of its more convenient priced feature. Thus, you can run your all test processes with it.
We have talked about free/paid test management tools you can use up to now. On the other side, there are other test types like performance, load and functional that you can actualize. Now, I want to introduce you a lifesaver: JMeter which can test dynamically produced SOAP (Simple Object Access Protocol) and REST (Representational State Transfer) based web services besides static files like HTML, image, CSS, js.
JMeter: JMeter is a %100 java language based test tool that’s why Java Runtime Environment (JRE) or Java Development Environment (JDK) should be downloaded on your device. JMeter saves the test plans as XML format and provides you use over and over again. It is open source and can be run with multi-threads. You are able to simulate user requests with it just like the real users make web requests while they’re using web applications. It uses HTTP protocol to seem as virtual user. A test plan given to JMeter determines which pages will be called when and with which information. It starts surfing your web pages by connecting to your application with HTTP protocol if the test plan is put in process in the direction of this information. Simulated test scenarios by it, web application requests and inputs can be fictionalized by differentiating just like more than one user are running the scenario at the same time.
Not finding any bugs in your product means you don’t have a bug with the current scenarios and methods you have, but you still may have bugs. It’s nearly impossible to test without any missing details. At that point, your risk factors should be counted and you should make your tests until see there is no risk according to your checks.
https://jmeter.apache.org/ & JMeter Application
https://www.gurock.com/testrail & TestRail Application
https://app.qase.io/projects & Case.io Application