Abstract:
Embodiments of the present invention disclose a method, computer program product, and system for comparing screenshots of an application interface. In one embodiment, the method includes receiving test scenario parameters, wherein the parameters include a first screenshot of an application interface, one or more page objects associated with the first screenshot, generating a second screenshot of an updated application interface, identifying one or more page objects within the second screenshot based on a scope of each of the page objects associated with the first screenshot, comparing a section of the second screenshot to a section of the first screenshot that includes one or more page objects associated with the first screenshot that correspond to one or more page objects included in the section of the second screenshot, and determining whether the section of the second screenshot matches, within a predetermined tolerance level, the section of the first screenshot.
Abstract:
A method for providing for standardization of variable names in an integrated development environment is provided. The method includes scanning a project source code for variable names, where the project source code is managed by a development team in an integrated development environment. The method includes determining that the project source code contains a non-standard variable name, where the distinction between a standard variable name and the non-standard variable name is defined by a set of standards and semantic rules. The method then includes identifying a location of the non-standard variable name in the project source code.
Abstract:
Embodiments of the present invention disclose a method, computer program product, and system for comparing screenshots of an application interface. In one embodiment, the method includes receiving test scenario parameters, wherein the parameters include a first screenshot of an application interface, one or more page objects associated with the first screenshot, generating a second screenshot of an updated application interface, identifying one or more page objects within the second screenshot based on a scope of each of the page objects associated with the first screenshot, comparing a section of the second screenshot to a section of the first screenshot that includes one or more page objects associated with the first screenshot that correspond to one or more page objects included in the section of the second screenshot, and determining whether the section of the second screenshot matches, within a predetermined tolerance level, the section of the first screenshot.
Abstract:
A method for providing for standardization of variable names in an integrated development environment is provided. The method includes scanning a project source code for variable names, where the project source code is managed by a development team in an integrated development environment. The method includes determining that the project source code contains a non-standard variable name, where the distinction between a standard variable name and the non-standard variable name is defined by a set of standards and semantic rules. The method then includes identifying a location of the non-standard variable name in the project source code.
Abstract:
A computer-implemented method, computer program product, and computing system is provided for automatically creating screen captures of a user interface. In an implementation, a method may include identifying a portion of a user interface display associated with a page object. The method may also include creating a screen capture image including the portion of the user interface display associated with the page object. The method may further include associating the screen capture image with a documentation record for the page object.
Abstract:
A computer-implemented method, computer program product, and system is provided for determining test coverage. In an implementation, a method may include identifying at least one change in source code. The method may also include instrumenting object code of at least one class file associated with a source file of the source code associated with the identified at least one change. The method may further include testing the instrumented object code with at least one test case. The method may further include generating a coverage report associated with the instrumented object code, wherein the coverage report includes a proportion of the at least one change in the source code covered by the at least one test case.
Abstract:
A method for testing a new workflowed item associated with a workflow process in a content management system (CMS) is provided. The method may include adding a workflow stage to the workflow process in the content management system (CMS). The method may also include adding a test associated with the workflow stage. The method may further include determining if a criteria threshold is met based on the test associated with the workflow stage. Additionally, the method may include publishing the new workflowed item based on the criteria threshold being met.
Abstract:
A computer-implemented method, computer program product, and computing system is provided for generating software patches. In an implementation, a method may include receiving an indication of a software product and a product level of the software product. An indication of a specific defect associated with the software product and the product level may be received. A defect change-set associated with a correction of the specific defect may be identified. An overlapping change-set may be determined based on, at least in part, a source control history associated with the software product. The overlapping change set may occur between the product level and the defect change-set in the source control history and may implicate at least one common file with the defect change-set. A software patch correcting the specific defect may be generated based on the defect change-set and the overlapping change-set.
Abstract:
A method, computer program product, and computer system for receiving, at a computing device, an input including an indication of a type of an object for which an instance is required. Code that is declared in a software development application is scanned for the instance. An output is generated including one or more suggestions how to acquire the instance based upon, at least in part, the code that is declared in the software development application.
Abstract:
A computer-implemented method, computer program product, and computing system is provided for generating software patches. In an implementation, a method may include receiving an indication of a software product and a product level of the software product. An indication of a specific defect associated with the software product and the product level may be received. A defect change-set associated with a correction of the specific defect may be identified. An overlapping change-set may be determined based on, at least in part, a source control history associated with the software product. The overlapping change set may occur between the product level and the defect change-set in the source control history and may implicate at least one common with the defect change-set. A software patch correcting the specific defect may be generated based on the defect change-set and the overlapping change-set.