A Reflection on the Connection between Cloud Computing Concepts and There Application in Software QA Testing
In my cloud computing course, I expanded my knowledge in the area of cloud computing roles and boundaries, cloud characteristics, cloud delivery models, data centre technology and virtualization technology. Cloud computing roles and boundaries bring to light the cloud providers, consumers, organizational boundary, trust and resources. The information is vital in identifying what resources can be utilized in software QA testing. Cloud characteristics, on the other hand, enhanced my skill about the usage of cloud resources, concepts such as on-demand access, the elasticity of service, resource pooling, and resiliency. Similarly, cloud delivery model broadened my understanding of infrastructure as a service, platform as a service and software as service models. The delivery model, on the other hand, proved vital in identifying which model to adopt during software QA testing. The concepts learned in data centre technology include, virtualization, remote operation and management and network hardware and facilities. Finally, virtualization technology enlightened me on virtualization management, and resources replication.
Delegate your assignment to our experts and they will do the rest.
The learned skills are applicable in my job as a software QA tester by performing software functional tests, non-functional, test and ability testing. I can perform software functional test by the use of cloud-based resources such as Sauce Labs, Rapise and time shift X to perform system testing, acceptance testing, and integration testing. The QA tests establish compliance to system requirement, customer needs, and compatibility with various platforms that are accessible on the platform as a product model respectively. Non-functional testing, on the other hand, can be performed using cloud tools such as CloudTestGo, AppPerfect, AppLoader and CloudTest. The tools offer me a chance to perform business requirement testing, security testing, and scalability and performance testing. The test is aimed at establishing the software availability and ability to meet the business demands, safe handling of data, and ability to handle the intended number of users respectively. Lastly, software ability testing can be performed using cloud resources such as Quorum, ClickTest, CloudArray, and BrowserStack. The QA test involves checking for disaster recovery, compatibility and multi-tenancy. As such, I check whether the system can recover quickly with minimum data loss in the event of a disaster, the software’s compatibility of various platforms and the software availability in the event it is used by multiple users simultaneously, respectively.
A Reflection on the Connection between Analyzing and Visualizing Data Concepts and There Application in Software QA Testing
In my data analysis and visualization course, I expanded my knowledge in areas such as data exploration, data analysis and data presentation. Data explorations involved the modeling of data sets into a graphical representation that can easily tell about the unknown and also enable formulation of hypothesis. Data analysis, on the other hand, involves the utilization of the modeled data in confirming or rejecting the hypothesis and formulation of reason. Lastly, representation gave me more understanding of how to present information in a manner that is easy to understand.
I can apply the learned concepts of data analyzing and visualization to report on bugs; carry out visual review mock-ups, future ideas development and review tech specification; and adding a visual element in the software product testing. I found it prudent to incorporate visual aids such as screen-captures of bugs, videos recordings of the bugs activity and demonstration on my computer whenever it is hard to recreate the bug. This form of reporting helps the developer understand faster and resolve the problem as opposed to just documenting the steps used in generating the bug. On the other hand, visual review of mock-ups, future ideas development and tech specification involve the development of a visual representation of the mock-up. For example, I may need to draw what I have understood from the documentation. I can also analyze the developers’ mock-up visual representation to establish whether it translates to the provided text. As such, it is easy to analyze the software functionality, ability to meet the set expectation and possible future developments. Lastly, adding visual representation in software testing involved capturing the specific details of the software outputs such as the user interface, web pages, and data input option. The visual representation enhances the identification of wrong scales, disproportional user interface and distorted fonts and forms among other software problems.
